SAS 9.4 SMC Unresponsive when checking Libaray Property Dataserver tab

[JuanS_OCS]

Hi,

just as follow up: could you have any progress on this?

[Prab]

Hi, We have tried with double te memory settings for SASMC.ini.

But it didnt help...We have opened a SAS Track.

Thank you.

Prabhu

[SASKiwi]

Not sure if you read my last response about how to create a data connection to Oracle outside of metadata (using a SAS LIBNAME statement). I think it would be very useful to confirm if a connection works well outside of metadata or not.

[JuanS_OCS]

I would follow SASKiwi 's suggestion

[Prab]

HI..I forgot to update this point.

I have tried executing below SAS Library statement from SAS EG. It was executing fine.

libname or oracle path="&ora_path" user="&ora_auser" password="&ora_apassword"

ADJUST_BYTE_SEMANTIC_COLUMN_LENGTHS=YES
ADJUST_NCHAR_COLUMN_LENGTHS=YES DBCLIENT_MAX_BYTES=1;

Please correct me If I wrong in understanding "create a data connection to Oracle outside of metadata"?

[JuanS_OCS]

What I think SASKiwi meant was to run this libname on a SAS Base, and no connection to the metadata.

If it runs just fine on SAS Base from your server, it means there is something wrong on the metadata.

Is this happening the same with all Oracle connections? Or only this connection?

I wonder: did you tried, just for "fun and giggles" to create a new connection and library to the same server/schema, from scratch?

[Prab]

HI,

Please find my answers next to your queries.

If it runs just fine on SAS Base from your server, it means there is something wrong on the metadata.

It was running fine from SAS BAse Layer.
 

Is this happening the same with all Oracle connections? Or only this connection?
It was happening with ALL oracle lib connections.

I wonder: did you tried, just for "fun and giggles" to create a new connection and library to the same server/schema, from scratch?
Yes, Tried and found same unresponsive.

THanks

[Prab]

Do you think can we get any clues from ORACLE DB side???

[JuanS_OCS]

It is possible, yes. I would check first the logs on the oracle driver. SysAdmins can probably help you with enabling and looking into the logs of the Oracle driver.

[Prab]

Thank you.Apart from setting logging level in SASSMC.ini..

Do you have any other logging options ??

[JuanS_OCS]

Well, besides the libname, you could try to update your metadata from SAS Base too:

http://support.sas.com/documentation/cdl/en/bidsag/61236/HTML/default/viewer.htm#a003114182.htm

Secondly, for anything related to databases, you have sastrace options: http://support.sas.com/documentation/cdl/en/engfedsrv/65922/HTML/default/viewer.htm#n167fxh8cc9h2an1...

[Prab]

HI,

Thank you..

As you know..we didnt have any issues in DEV.

I am not sure how to troubleshoot/verify DEV with PROD...I am looking where can we find insights about differences in any config.

Thanks

[JuanS_OCS]

Indeed, on those cases, it is hard to qualify the impact and root of a possible difference between environments.

My approach would go to try to discard any business/functional differences, then go into the technical. I would suggest to give a quick look to the technical blueprint of your architecture/deployment, to know which components are involved, then evaluate on each of them, including the network components such as firewalls etc if needed, as last resort.

PS. if you are on Windows, you can give a look to the Windows Logs, and in UNIX systems, to the sys logs. Any important error should be logged there, independant of it is a system, security or application error.

[Prab]

Thanks .

I found below error from Metadata Server log..Any idea about below TRACE??

SASMeta_MetadataServer_console_XXX-sas94-meta-prod.log_0939_16022016

ERROR: The system has encountered an unhandled Exception.
     : Please contact technical support and provide them
     : with the following traceback and system dump information:

ABORT:   SAS/TK is aborting
     :  Abort Log file [tk.reportlog.863663]
     :  ---------------------------------------
     :  Time [2/09/2016  10:27:48 PM]
     :  ---------------------------------------
     : Thread Name [KeepAliveThread]

 Traceback:

/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bkt_abort_tkt_cb+0xa2) [0x7fac253edb22]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(skaCallAbortRoutines+0x111) [0x7fac253ecb81]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bkabort+0x84) [0x7fac253f7c74]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7fac253ea5d4]
/lib64/libpthread.so.0(+0xf710) [0x7fac2660f710]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkersa2.so(UpdateHashWithSecretKey+0x8c) [0x7fabe97477cc]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkersa2.so(+0x1f220) [0x7fabe973f220]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiomsam.so(+0xf269) [0x7fabb000c269]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiomsam.so(+0xe22d) [0x7fabb000b22d]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiompeb.so(pebPushPacket+0x6c3) [0x7fabb04cacf3]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiompeb.so(tkiompebKeepAliveThreadMain+0x7a2) [0x7fabb04aa072]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(sktMain+0x94) [0x7fac253e8214]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bktMain+0x69) [0x7fac253e9df9]
/lib64/libpthread.so.0(+0x79d1) [0x7fac266079d1]
/lib64/libc.so.6(clone+0x6d) [0x7fac25c958fd]

ERROR: The system has encountered an unhandled Exception.
     : Please contact technical support and provide them
     : with the following traceback and system dump information:

ABORT:   SAS/TK is aborting
     :  Abort Log file [tk.reportlog.3470718]
     :  ---------------------------------------
     :  Time [2/16/2016  7:41:47 AM]
     :  ---------------------------------------
     : Thread Name [KeepAliveThread]

 Traceback:

/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bkt_abort_tkt_cb+0xa2) [0x7f48c2f6ab22]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(skaCallAbortRoutines+0x111) [0x7f48c2f69b81]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bkabort+0x84) [0x7f48c2f74c74]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f48c2f675d4]
/lib64/libpthread.so.0(+0xf710) [0x7f48c418c710]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkersa2.so(UpdateHashWithSecretKey+0x8c) [0x7f488726d7cc]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkersa2.so(+0x1f220) [0x7f4887265220]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiomsam.so(+0xf269) [0x7f484d85a269]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiomsam.so(+0xe22d) [0x7f484d85922d]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiompeb.so(pebPushPacket+0x6c3) [0x7f484dd18cf3]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkiompeb.so(tkiompebKeepAliveThreadMain+0x7a2) [0x7f484dcf8072]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(sktMain+0x94) [0x7f48c2f65214]
/opt/sas/sas94/SASFoundation/9.4/sasexe/tkmk.so(bktMain+0x69) [0x7f48c2f66df9]
/lib64/libpthread.so.0(+0x79d1) [0x7f48c41849d1]
/lib64/libc.so.6(clone+0x6d) [0x7f48c38128fd]

[JuanS_OCS]

This is a SAS/CONNECT / remote sessions related issue. Are you working with a SAS Metadata cluster?

Besides, is this error happening after each DB error? Can you confirm?

We need to be clear and not confuse/mix errors.

Please find more information about your error here (just selected a clear message of your log "SAS/TK is aborting" and googled it):

http://support.sas.com/kb/56/228.html

http://support.sas.com/kb/56/751.html

http://support.sas.com/kb/45/960.html

http://support.sas.com/kb/57/661.html <-- I don't think it is your case, but in case you work with Grid Manager, it might be of your interest.