Segmentation violation error

Reply
Occasional Contributor
Posts: 8

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: 6,502

Re: Segmentation violation error

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;
Regular Contributor
Posts: 190

Re: Segmentation violation error

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.

 

 

Ask a Question
Discussion stats
  • 2 replies
  • 228 views
  • 0 likes
  • 3 in conversation