If the LD_LIBRARY_PATH_64 environment variable is defined on Solaris, you may receive various errors when running SAS® programs. The errors will be similar to the following:

   fatal: libmtsk.so.1: open failed: No such file or directory

   ERROR: ld.so.1: sas: fatal: libsunperf.so.6: open failed: No such file or directory

The issue is that if LD_LIBRARY_PATH_64 is defined, then only the paths it contains will be searched for linking 64-bit shared objects. SAS, however, relies on the LD_LIBRARY_PATH environment variable and modifies its value to include the additional paths required for SAS to run correctly.

To circumvent this issue, use one of the following methods:

1. Unset LD_LIBRARY_PATH_64, adding any unique paths it contains to LD_LIBRARY_PATH
2. Modify !SASROOT/bin/sasenv_local and add the following lines:
   
   
   if [ -n "$LD_LIBRARY_PATH_64" ]
   then
   LD_LIBRARY_PATH_64=$JAVA_HOME/lib/sparc/server:$JAVA_HOME/lib/sparc:$SAS_INSTALL_ROOT/sasexe:$LD_LIBRARY_PATH_64
   export LD_LIBRARY_PATH_64
   fi
   

The first method will ensure both 32-bit and 64-bit linking is done using the paths contained in the value of LD_LIBRARY_PATH. The second method will add the paths required by SAS to the existing value of LD_LIBRARY_PATH_64.

Operating System and Release Information