Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

You may receive an error message containing garbage characters when
using the SAS/ACCESS Interface to Oracle.  The error message may
resemble:

  libref      ÿÿÿÿh¡ú
  ERROR: Error in the LIBNAME statement

where libref is the library reference for your LIBNAME statement.

Another example of how this problem manifests itself in the SAS Log:

SASHELP "$P CODE

This error seems to be generated when the ORACLE_HOME environment
variable is not set in the SAS session.  Either you do not have
ORACLE_HOME specified correctly in the system path on WINDOWS or on
UNIX the ORACLE_HOME environment variable is not set or not set
correctly, OR there may be a mixed Oracle installation.

To correct the problem on UNIX, set the ORACLE_HOME environment variable
prior to invoking your SAS session or add the environment variable to
the sasenv/sasenv_local file located in the !SASROOT/bin
directory (where !SASROOT is the location of your SAS installation).

TO correct the problem on WINDOWS, set the windows SYSTEM PATH to
contain the correct ORACLE_HOME.

The best way to determine exactly how environment variables are set for
a SAS session with Data Step code with a FILENAME PIPE.  Please see
Usage Note  #014758 .

This error may also be issued when the Oracle installation is incorrect.
In one customer scenario, they had mixed 32-bit and 64-bit Oracle
libraries installed in the same client library directory.  Once the
installation was corrected this error disappeared.  Another customer had
permission issues in the Oracle client libraries directory.  Once the
permissions were modified so the libraries could be read by the user(s),
this error disappeared.

Operating System and Release Information