BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
MariaD
Barite | Level 11

Hi Folks,

 

We have installed Oracle Client 12c on our Linux server. Using SAS Deployment Manager we configure SAS Access to Oracle to 12c. We also added the following environment variables on sasenv_local under../SASFoundation/9.4/bin:

 

export LD_LIBRARY_PATH=/oracle/product/12.2.0/client_1/lib:$LD_LIBRARY_PATH

export PATH=/oracle/product/12.2.0/client_1/bin:$PATH

export TNS_ADMIN=/oracle/product/12.2.0/client_1/network/admin:$TNS_ADMIN

export ORACLE_HOME=/oracle/product/12.2.0/client_1:$ORACLE_HOME

 

Before test the new library, we restarted our services but when we tried to create a oracle libname we had the following error:

 

26         LIBNAME ORALIB ORACLE  PATH=AAAA  SCHEMA=MY_SCHEMA  USER=user

26       ! PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;

ERROR: Unable to connect to Oracle-Oracle environment is either not set or set incorrectly!

ERROR: Error in the LIBNAME statement.

 

Any idea what is missing?

1 ACCEPTED SOLUTION

Accepted Solutions
MariaD
Barite | Level 11

Thanks to all. We reviewed the environment variables definition and we find an extra "/" that cause the problem.

 

Regards,

View solution in original post

3 REPLIES 3
SASKiwi
PROC Star

I suggest you try a test query in Oracle's SQLPLUS tool on your SAS server. If it works then there is something on the SAS side that is not configured correctly. If it doesn't work, then it is an Oracle client configuration problem and nothing to do with SAS. Make sure you have the correct database connections defined in your TNSNAMES.ORA file.

ankitd
Obsidian | Level 7

My initial understanding is that you need to define the ODBCINI and ODBCINST path as well apart from that ensure that you LD_LIBRARY_PATH has everything covered.

 

The best validation is to verify whether the isql test works fine, in case that fails then you need to understand whether there is some firewall issue, if the isql test works fine then you are confined to just the SAS configuration.

 

Worth trying the above two before we can look at other possibilities.

 

Regards,

Ankit

MariaD
Barite | Level 11

Thanks to all. We reviewed the environment variables definition and we find an extra "/" that cause the problem.

 

Regards,

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 1470 views
  • 0 likes
  • 3 in conversation