Hi @Mastanvali
If few are able to connect then I believe the configuration is fine. I would suggest for the user who isn't able to login successfully to try connecting oracle from command line directly outside of SAS to validate he is able to connect. It's probably the environment variables required for oracle to function properly aren't set for few users. If user is able to connect from client, it should work from SAS as well.
Please see the steps below:
To use SAS/ACCESS Interface to Oracle, you must set the ORACLE_HOME environment variable. In addition, you must make sure that the shared library path variable (the name of this variable is operating system dependent) points to where the Oracle shared libraries are located. This is required since the SAS/ACCESS Interface to Oracle executable uses Oracle shared libraries and needs to know where they are located at your site.
If the environment variables are not set correctly, you will see error messages similar to the following when connecting to Oracle from SAS: ERROR: Could not load /app/SAS/SASFoundation/9.4/sasexe/sasora (86 images loaded) ERROR: Could not load module /app/SAS/SASFoundation/9.4/sasexe/sasora. Dependent module libclntsh.a(shr.o) could not be loaded.Could not load module libclntsh.a(shr.o).System error: No such file or directoryCould not load module /app/SAS/SASFoundation/9.4/sasexe/sasora. Dependent module /app/SAS/SASFoundation/9.4/sasexe/sasora could not be loaded. ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded. ERROR: Image SASORA found but not loadable. ERROR: Error in the LIBNAME statement.
Source: Configuration Guide for SAS 9.4 Foundation for UNIX Environments
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to explore data assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.