Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
The djxlinkSybase script reports that the libdb2ctlib library was linked successfully even if it was not. To re-create the error: (1) Set environment variable SYBASE to a dummy directory that does not contain the needed Sybase client libraries. (In order to fool the script into thinking that the dummy directory is a valid Sybase client directory, it must contain directory $SYBASE_OCS/lib.) (2) Go to the bin subdirectory of the DB2 install directory and run ./djxlinkSybase. You will see results similar to the following. Note that the script reports the library was built successfully even though it was not. $ ./djxlinkSybase SYBASE = /home2/user/sybase_dummy SYBASE_OCS = OCS-12_5 nm: /home2/user/sybase_dummy/OCS-12_5/lib/libcs_r64.a: 0654-200 Cannot open the specified file. nm: No such file or directory nm: /home2/user/sybase_dummy/OCS-12_5/lib/libct_r64.a: 0654-200 Cannot open the specified file. nm: No such file or directory nm: /home2/user/sybase_dummy/OCS-12_5/lib/libxadtm64.a: 0654-200 Cannot open the specified file. nm: No such file or directory Linking library "libdb2ctlibF.a" with version "12.5" of client... An error occurred building library "libdb2ctlibF.a". Linking library "libdb2ctlibF.a" with version "12.5" of client... Library "libdb2ctlibF.a" was built successfully. chmod: libdb2ctlibF.a: No such file or directory
Local fix
The problem can be fixed as follows: (1) Edit file djxlinkSybase (in the bin subdirectory of the DB2 install directory) and locate the following line, which is usually the second or third line from the end of the script: check_build_results $? $my_target_library (2) Change the line to: check_build_results $rc $my_target_library Once you fix the above problem, you will still need to fix the problem that caused the link to fail. One common cause of that problem is not installing the Sybase XA Interface Library. To do that, when you install the Sybase client, you must specify the Full or Custom option. If you specify the custom option, select the XA Interface Library for ASE Distributed Transaction Manager option. For more details, see http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?top ic=/com.ibm.websphere.ii.foundation.conn.fw.syb.doc/configuring/ tlssyb01.html
Problem summary
Users affected: Users of the Sybase wrapper in InfoSphere Federation Server Problem description and summary: See error description
Problem conclusion
Problem was first fixed in Version 9.1, FixPak 7 (s090308). This fix should be applied on the federation server.
Temporary fix
Comments
APAR Information
APAR number
JR28587
Reported component name
SYBASE WRAPPER
Reported component ID
5724N9711
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-02-27
Closed date
2009-05-11
Last modified date
2009-05-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SYBASE WRAPPER
Fixed component ID
5724N9711
Applicable component levels
R910 PSN
UP
R911 PSN
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
24 May 2022