02-09-2016 04:52 PM
I have a SAS environment 9.4 on one server and Oracle database on other server.Now for some reasons we need to change the oracle server as well Oracle SID, but the main concern is how to adapt the SAS environment with this new modification. could kindly explain how please?
02-09-2016 06:02 PM
What SAS product do you use to communicate with Oracle? SAS/ACCESS to Oracle or something else?
You will most likely have Oracle client software installed on your SAS server containing a setup file called TNSNAMES.ORA. This file needs to be configured with your new server settings.
02-10-2016 05:59 AM
SAS/ACCESS to Oracle is existing but can't load the error appear as below :
ERROR: Could not load /home/u01/SASHome/SASFoundation/9.4/sasexe/sasora (57 images loaded)
ERROR: libclntsh.so.11.1: cannot open shared object file: No such file or directory
143 LIBNAME tst_lib ORACLE PATH=EEALBB USER=casemgmt PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;
ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded. ERROR: Image SASORA found but not loadable..
Please make sure Oracle environment is set correctly.
Look in the install/Config doc for additional info for your platform.
Other possible reasons - incomplete Oracle client install, 32/64-bit mismatch between Oracle client & SAS, incorrect Oracle client
version(Oracle client must match the version picked during post-install process), incompatible sasora for your OS or its
attribs don't permit SAS to load it.
ERROR: Error in the LIBNAME statement.
02-10-2016 07:55 AM
02-10-2016 08:41 AM
02-10-2016 08:54 AM
Here's the SAS documentation regarding session encoding and how to change it:
Alternativley, you should be able to just add a parameter to the sasv9_local.cfg file in <sashome>/SASFoundation/9.4.
You would add an option in this file. It should look something like this: -ENCODING utf-8
In my environment, we originally configured as utf-8, but then I realized that alot of people that would be migrating from old servers to the new servers had all of their datasets encoded with latin1. So we added "-ENDODING utf-8" to the sasv9_local.cfg file.
02-10-2016 10:15 AM
Need further help from the community? Please ask a new question.