Thanks...This DataServer Tab details appear in Folder Tab...not from Plug-Ins Tab. I mean I cant see Library Manager from Plug-Ins Tab.       Do you still stick to your point ??     PFA. ... View more

HI All,   One quick update...   I can able to see SAS 9.4 SMC- data server tab details with SASTRUST user Only.   Not sure how to proceed from here ?? ... View more

Hi All, One quick update..   Yesterday I had a chance to restart Metadata Server. (It went down unexpectedly!!)   In Restart Metadata Server log I found below errors:   2016-03-01T15:51:44,421 INFO  [00000006] :xxxxxxxp - 2016-03-01T15:51:44,637 INFO  [00000004] :xxxxxxxp - SAH011001I SAS Metadata Server (8561), State, starting 2016-03-01T15:51:44,800 INFO  [00000008] :xxxxxxxp - The maximum number of cluster nodes was set to 8 as a result of the OMA.MAXIMUM_CLUSTER_NODES option. 2016-03-01T15:51:44,803 INFO  [00000008] :xxxxxxxp - OMACONFIG option 1 found with value OMA.SASSEC_LOCAL_PW_SAVE and processed. 2016-03-01T15:51:44,881 INFO  [00000008] :xxxxxxxp - Using AES for password storage. 2016-03-01T15:51:44,882 INFO  [00000008] :xxxxxxxp - Using SASPROPRIETARY for password fetch. 2016-03-01T15:51:44,882 INFO  [00000008] :xxxxxxxp - Using SHA-256 for password hash. 2016-03-01T15:51:44,912 INFO  [00000008] :xxxxxxxp - SAS Metadata Authorization Facility Initialization. 2016-03-01T15:51:44,912 INFO  [00000008] :xxxxxxxp - xxxxxxxp is an adminUser. 2016-03-01T15:51:44,912 INFO  [00000008] :xxxxxxxp - SASTRUST@SASPW is a trustedUser. 2016-03-01T15:51:44,918 INFO  [00000008] :xxxxxxxp - SASADM@SASPW is an unrestricted adminUser. 2016-03-01T15:51:45,038 INFO  [00000013] :xxxxxxxp - User libref, RPOSMGR, assigned to path, /var/opt/data/sas/sas94/configMETA/Lev1/SASMeta/MetadataServer/rposmgr, wit h server libref, I0000001. 2016-03-01T15:51:45,052 INFO  [00000013] :xxxxxxxp - User libref, TMP000, assigned to path, /var/opt/data/sas/sas94/configMETA/Lev1/SASMeta/MetadataServer/MetadataRepos itories/Foundation, with server libref, I0000002. 2016-03-01T15:51:45,289 INFO  [00000008] :xxxxxxxp - OpenRepository Id=A57BYNRC, Name=Foundation, PauseState=ONLINE, RepositoryFormat=16, Model=16.01. 2016-03-01T15:51:52,572 INFO  [00000013] :xxxxxxxp - User libref, TMP001, assigned to path, /var/opt/data/sas/sas94/configMETA/Lev1/SASMeta/MetadataServer/MetadataRepos itories/BILineage, with server libref, I0000003. 2016-03-01T15:51:52,574 INFO  [00000008] :xxxxxxxp - OpenRepository Id=A5D7VHK6, Name=BILineage, PauseState=ONLINE, RepositoryFormat=16, Model=16.01. 2016-03-01T15:51:52,577 INFO  [00000008] :xxxxxxxp - Initializing journal file: Journal/2016-02-29T07_07_28+01_00_Journal.dat 2016-03-01T15:51:52,577 INFO  [00000008] :xxxxxxxp - Using the TKR compression algorithm for the journal file. 2016-03-01T15:51:52,577 ERROR [00000008] :xxxxxxxp - The size of this journal file was recorded in the backup manifest as 1024 (0x400) when in fact it is 9183703 (0x8c2 1d7) bytes. 2016-03-01T15:51:52,577 ERROR [00000008] :xxxxxxxp - A journal inventory is being performed to correct the manifest. 2016-03-01T15:51:52,577 INFO  [00000008] :xxxxxxxp - Rewinding the journal file, dump of structure before: 2016-03-01T15:51:52,577 INFO  [00000008] :xxxxxxxp - Rewinding the journal file, rewind value=1, position=1024. 2016-03-01T15:51:52,578 INFO  [00000008] :xxxxxxxp - jnlfileRewind: fileSize=9183703           8c21d7. sizeof(fileSize)=8 2016-03-01T15:51:52,578 INFO  [00000008] :xxxxxxxp - jnlfileRewind: codepath 3 lRewindSizeValue=9182679. 2016-03-01T15:51:52,578 INFO  [00000008] :xxxxxxxp -                                   rewind size value=9182679. 2016-03-01T15:51:52,667 INFO  [00000008] :xxxxxxxp -       return code from rewind =        0. 2016-03-01T15:51:52,667 INFO  [00000008] :xxxxxxxp - jnlfileRewind: lRewindSizeValue=(9182679) or (0x00000000008c1dd7). 2016-03-01T15:51:52,667 INFO  [00000008] :xxxxxxxp -       return code from rewind =        0. 2016-03-01T15:51:52,667 INFO  [00000008] :xxxxxxxp - Rewinding the journal file, dump of structure after: 2016-03-01T15:51:52,875 INFO  [00000008] :xxxxxxxp - Journal inventory complete. 5055 entries with entry numbers from 566606 to 571660. 2016-03-01T15:51:52,875 ERROR [00000008] :xxxxxxxp - Journal inventory updating manifest and GCB to reflect highest journal entry number as 571660 and GUID as 404FBBBD- 2050-3646-B726-241789E4F092. ... View more

One correction: We use secure libraries. ... View more

Hi, Please see my answers next to your queries.   do you eperience this problem no matter what user logs on to SASMC? if you use sasadm@saspw , and you do have another admin user - just for the fun of it - try to log on with the other admin user ID and try again.   Ans:  Yes..Same issue persists.   Are you using Metadata bound libraries? No   My apologies if this has been answered before: you are using SAS/Access to Ora? Yes. ... View more

Hi, I am sorry..I thouht it might one of cause..   Are you working with a SAS Metadata cluster? Yes.   Besides, is this error happening after each DB error? Can you confirm? No ..This is not happening along with ORACLE DB. ... View more

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] ... View more

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     ... View more

Thank you.Apart from setting logging level in SASSMC.ini..   Do you have any other logging options ?? ... View more

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

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 ... View more

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"? ... View more

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 ... View more

Sure ..Thank you very much for your answer.   We will check in that direction. ... View more