• Print |
• E-mail  |
• Bookmark

The following message may be issued to the shell when attempting to
access Oracle 9 on Digital Unix:

  WARNING libaio_raw:  A previous initialization of libaio has been
     detected.  The libaio_raw and libaio libraries cannot be linked
     into the same image or undefined behavior will result.  Only libaio
     or libaio_raw should be used.

The problem is that SAS is linked against libaio indirectly through some
other Tru64 libraries that SAS links against.  Oracle is linked against
libaio_raw.  The two libraries don't exist together well and usually the
end result is the above message or a hang when they interfere with one
another.  Starting with Tru64 5.1a PK4 and later, Compaq is at least
issuing the warning that the user is now seeing to alert folks that
using libaio and libaio_raw together is not officially supported and
undefined behavior may result.

The undefined behavior that we have witnessed in the past has been
that SAS would hang and not respond. We've never seen data corruption
though.

However, Compaq and Oracle were having difficulty determining whose
problem this was.  Compaq provided the warning note as their response to
the issue and Oracle indicates that this was resolved at Oracle 9.2.0.2
(Oracle bug #2345096)

Please run the following command to determine if you are running with
the fixed library or not:

  odump -Dl  $ORACLE_HOME/lib/libclntsh.so.9.0

An output similar to the following will be generated.

  ***LIBRARY LIST SECTION***
        Name             Time-Stamp         CheckSum   Flags Version
  /u01/app/oracle/product/9.2.0/lib/libclntsh.so.9.0:
        libwtc9.so   Jul 26 12:49:13 2003 0xa891dabd       0
        libexc.so    Oct 16 14:53:16 2002 0xb0f9a902       0 osf.1
        librt.so     Sep 28 17:33:45 2003 0x7ac6f184       0 osf.1
        libaio_raw.so Oct 16 14:56:52 2002 0x2c023cc7      0 osf.1
        libm.so      Oct 16 15:05:56 2002 0x07757304       0 osf.1
        libc.so      Sep 28 17:21:44 2003 0xcbc4092f       0 osf.1
        libpthread.so Apr 14 17:43:39 2003 0x2fed6b4a      0 osf.1

Oracle's fix for this (as detailed in Note: 202282.1) is to provide two
client libraries:  libclntsh.so.9.0 and libclntsh_aio.so.9.0.  The first
is linked with libaio_raw.so and the latter is linked with libaio.so
according to the note.  For an application (such as SAS) that uses
libaio.so in other places, the proper fix is to link with
libclntsh_aio.so from Oracle.

To circumvent this problem, replace libclntsh.so.9.0 with a link to
libclntsh_aio.9.0,

Oracle's note 202282.1 available on Metalink explains the solution,
which is to provide two versions of libclntsh.so on Tru64.  If an
application links with libaio.so from HP, it should also link with
libclntsh_aio.so from Oracle.  If an application uses libaio_raw.so from
HP, then it should use libclntsh.so from Oracle.

Below is the link to find this note.  You will need an Oracle Metalink
login  (the link below wraps two lines so be sure you enter the entire
link when attempting to access the note.

http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_d
atabase_id=NOT&p_id=202282.1

This looks like Oracle's formal solution to these bugs:

   bug:2401838
   bug:2418184
   bug:2418195
   bug:2345096


A Technical Support hot fix for SAS 9.1.2 (9.1 TS1M2) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/c9_sbcs_prod_list.html#013306

For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/c9_dbcs_prod_list.html#013306



A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#013306

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#013306


After applying the hot fix, in some SAS/ACCESS to Oracle installations,
it was discovered that the sasora image shipped with our service pack
is a module and not a link.  The module appears to be linked with an
older version of the Oracle client libraries.  Therefore, creating a
symbolic link to point to the correct client version should correct
this problem.  Instructions for creating the link are as follows:

  unix_prompt> cd !SASROOT/hotfix/sasexe
  unix_prompt> mv sasora sasora.save

Operating System and Release Information

A fix for SAS 9.1.2 (9.1 TS1M2) for this issue is available at:

A fix for SAS 9.1.2 (9.1 TS1M2) with Asian Language Support (DBCS) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :