• Print |
• E-mail  |
• Bookmark

If you are using the Sybase Open Client 12.5.1 or above with the
SAS/ACCESS Interface to Sybase, you will receive the following error in
your SAS log:

  ERROR:  A Sybase Context Allocation Failed. sassyb:s_ctx: init of open
          client failed.
  ERROR:  A Connection to the sybase DBMS is not currently supported, or
          is not installed at your site.

You may also see the following Sybase Open Client error message:

  Message number: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (131)
  Message String: ct_init(): network packet layer: internal net library
     error:  Attempt to load protocol driver failed

In Release 12.5.1 and above of the Syase Open Client, Sybase changed the
manner in which they build their shared libraries.  Prior to Release
12.5.1 of the open client, Sybase build their libraries using big format
archived shared libraries which contained shared objects.  They are now
using true AIX shared libraries.

A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#012913

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#012913

Once the SAS 9.1.3 Service Pack is installed, the following instructions
must be  performed to complete this Sybase fix.

***REMINDER*** Remember, on AIX, the installer MUST submit the makefile
provided in order to statically build the "sassyb" appendage.  This must
happen each time that an upgrade is done to either a new sas release,
service pack upgrade and/or a new sybase client release.

Development is working with publications to provide the correct and
formal documentation needed on this issue in the Service Pack
Installation and Configuration Guide instructions.  However, in the
interim please follow the instructions below and re-test.

NOTE: you should replace !SASROOT in these instructions with the actual
directory path where SAS was installed.

1. Change to the directory !SASROOT/sasexe using the folling command:

    unix_prompt> cd !SASROOT/sasese

2. Use the following command to change permissions of the executable
   "syr64125":

    unix_prompt> chmod +w syr64125

3. Use the following command to remove the symbolic link "sassyb":

    unix_prompt> rm sassyb

4.  Change to the directory !SASROOT/misc/dbi/:

    unix_prompt> cd !SASROOT/misc/dbi/

5.  Follow the instructions in the text file, sassyb.txt, which I have
    copied the information from this text file below for your reference.

-----------------------------------------------------------------------
Install Instructions to allow SAS 9.x to work with Sybase Open Client
12.5.x on AIX 5.x
------------------------------------------------------------------------

Note: !SASROOT in the instructions below refers to the path of the SAS
      root directory.  If you don't know the location of SASROOT, please
      contact your SAS representative.

Note2: Please be sure to have the SYBASE environment variable defined.
       If it is not defined, the makefile will fail.  Example on how to
       set the SYBASE environment variable:

       export SYBASE=/usr/local/sybase/1252
------------------------------------------------------------------------

(a)  Change to the directory !SASROOT/misc/dbi/:

     unix_prompt> cd !SASROOT/misc/dbi/

(b)  Restore the !SASROOT/misc/dbi/sassyb.tar file:

     unix_prompt> tar -xvf sassyb.tar

(c)  After the files has been extracted, the following directory
     structure containing libraries and object files for linking
     will be created:

     unix_prompt> !SASROOT/misc/dbi/sassyb_obj/

(d) Run the makefile to build the image "syr64125" in !SASROOT/sasexe:

    unix_prompt> make -f sassyb.mak

This will create "syr64125" image in !SASROOT/sasexe as well as a soft
link named "sassyb" which points to the "syr64125" image.

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

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