When performing a new installation of SAS on Unix, if you choose "Load
All Licensed Software," SASSETUP will notify you if ACCESS modules are
licensed and will tell you that these ACCESS modules require
configuring. SASSETUP will give you the option of configuring these
ACCESS modules immediately or at a later time.

If you choose to configure these modules, SASSETUP will prompt you for
the release of the database you are running, then create the
appropriate link in !SASROOT/sasexe to point to the correct pre-linked
module.

For example, if you are configuring ACCESS to Oracle with SAS
9 on HP/UX and you indicate that you are using the
Oracle 8.1.7 client, then a link is created from sasora to orh64810.
If, however, you choose not to configure ACCESS to Oracle during the
installation process, SASSETUP nevertheless creates a module called
sasora in !SASROOT/sasexe. It is important to note that this module
is *not* a link, amd it may cause problems later.

This generic sasora module does not match up with any of the pre-linked
modules that SAS provides to accomodate different releases of Oracle,
as shown in the test below, and it seems to work only against relatively
old releases of Oracle.

  $ pwd
  /TECH/sasswl/HPUX.V9/sasexe
  $ ls -l sasora orh*
  -rwxr-xr-x   1 sasts      r&d          29288 Aug  1  2002 orh64810
  -rwxr-xr-x   1 sasts      r&d          29288 Aug  1  2002 orh64900
  -rwxr-xr-x   1 sasts      r&d          29288 Aug  1  2002 sasora
  $ sum orh64810
  39148 58 orh64810
  $ sum orh64900
  41117 58 orh64900
  $ sum sasora
  39048 58 sasora

This behavior seems to affect all SAS/ACCESS modules.  For example, SAS
creates a generic sassyb for ACCESS to Sybase and a generic sasnfx for
ACCESS to Informix even when you have chosen not to configure these
modules. As with ACCESS to Oracle, the generic modules do not match up
with any of the pre-linked modules SAS provides for these databases.

To correct this problem, you should remove the incorrect module that you
have been given by default and create a new link to the
correct pre-linked module. For the Oracle on HP/UX example above, the
circumvention would be:

  rm !SASROOT/sasexe/sasora
  ln -s !SASROOT/sasexe/orh64810

Operating System and Release Information