Segmentation violation error

Reply
Occasional Contributor
Posts: 9

Segmentation violation error

Any one has suggestions for this error? We have 9.4 M3 on Linux64 and this code connects to Hadoop via Impala access engine.

 

ERROR: An exception has been encountered.

Please contact technical support and provide them with the following traceback information:

 

The SAS task name is [SQL (2) ]

Segmentation Violation

 

Traceback of the Exception:

 

/sas/9.4/prod/install/SASFoundation/9.4/sasexe/sas(+0x15aa8e) [0x7fcef18daa8e]

/sas/9.4/prod/install/SASFoundation/9.4/sasexe/sas(+0x4cb0b) [0x7fcef17ccb0b]

/sas/9.4/prod/install/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7fceefd7d3c4]

/lib64/libpthread.so.0(+0x31ace0f7e0) [0x7fcef113e7e0]

 

SAS WTABORT (SQL (2)) The SAS System has detected an abort condition. An Exception occurred during wthtrm().

 Please Contact Technical Support.

Tasks

 

[MAIN   ] [WAITING ] pri[   5] reb[E64CF220] WC[0] WN[1]

[IDLETASK] [READY   ] pri[   9] reb[E64CF220]

[EVENTTSK] [WAITING ] pri[   0] reb[E64CF220] WC[0] WN[1]

[sasxkern] [WAITING ] pri[   3] reb[E64CF220] WC[0] WN[1]

[Session ] [WAITING ] pri[ 3] reb[DDFEABA0] WC[0] WN[1]

[TKSRV   ] [WAITING ] pri[   3] reb[DDFEB200] WC[0] WN[1]

[Object S] [WAITING ] pri[   7] reb[DDFEBC20] WC[0] WN[1]

[DOSSCHT ] [WAITING ] pri[   7] reb[DDFEBC20] WC[0] WN[1]

[OBJECT_E] [WAITING ] pri[   7] reb[DC35AD40] WC[0] WN[1]

[SASLPXAM] [WAITING ] pri[   7] reb[DC35AD40] WC[0] WN[1]

[SASODR ] [WAITING ] pri[   3] reb[BC0F4220] WC[0] WN[1]

[DOSSCHT ] [WAITING ] pri[   7] reb[DDFEBC20] WC[0] WN[1]

[ODX Moni] [WAITING ] pri[   7] reb[DC35AD40] WC[0] WN[1]

[Submit ] [WAITING ] pri[   3] reb[DC35AD40] WC[0] WN[1]

[SQL (2) ] [RUNNING ] pri[   7] reb[BC10CBA0]

Traceback

 

No Traceback Available

Super User
Super User
Posts: 7,752

Re: Segmentation violation error

Posted in reply to Priyanka_b

Having extra semi-colons in the middle of an SQL statement is probably not helping.

execute(
  set SYNC_DDL=1 /* ; */
) by impala;
execute(
  drop table if exists grn_raroc_uwa.&user._&acctList. purge /* ; */
)  by impala;
Valued Guide
Posts: 546

Re: Segmentation violation error

Posted in reply to Priyanka_b

Assuming that both the Proc SQL and Data _null_ steps are inside the macro you're making a fresh DB connection and disconnecting with every call - could there be some sort of memory leakage occuring? I'd expect thiat to be the root cause of a segmentation violation error.

 

 

Contributor
Posts: 21

Re: Segmentation violation error

Posted in reply to Priyanka_b

Hi, did you get a resolution to this?

We're on 94_M3, a recent Cloudera patch to 5.12.1 broke some fundamental code on the Hadoop side. Cloudera patched that, and now our queries are limited to 1000 rows per commit. Then, installing upgraded Jars and hotfixes has resulted in the Impala connection returning this error, even if you just try to view a table in EGuide.

Occasional Contributor
Posts: 9

Re: Segmentation violation error

Hello Dan, This error disappeared with re-run. We have not done any changes from SAS end.

Contributor
Posts: 21

Re: Segmentation violation error

Posted in reply to Priyanka_b

Fair enough, it turned out to be one of the SAS hotfixes that was causing the issue with communicating via the Impala engine for us.

Ask a Question
Discussion stats
  • 5 replies
  • 862 views
  • 0 likes
  • 4 in conversation