home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC69776 Status: Geschlossen

REMOVE DEPENDENCY ON LIBSTREAM.SO FROM LIBDB2.SO

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
There are two different C++ libraries.  One is classic (older 
one).  The other is standard (newer one).  Per HP, no executable 
should be dependent on both libraries.  HP warns that the result 
of mixing them includes unexpected failure. 
 
Although DB2 is built with the standard C++ library, it was 
found that libdb2.so, the client side library of DB2, is still 
linked with libstream.so, one of the classic C++ libraries. 
Through the fix for this APAR, libstream.so will be removed. 
 
 
Note that libdb2.so itself doesn't use any symbol from 
libstream.so.  In other words, the warning posed by HP does not 
apply to DB2 itself. 
 
Important Note: If an application, which links with libdb2.so, 
somehow references any symbol in the classic C++ library, and if 
it had been accessing them via libdb2.so in the past, it won't 
be able to access them after applying the fix for this APAR. 
The correct action is to fix the application to remove any 
dependency on the classic C++ library.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Applications that run on HP platform and link with libdb2.so * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* There are two different C++ libraries.  One is classic       * 
* (older                                                       * 
* one).  The other is standard (newer one).  Per HP, no        * 
* executable                                                   * 
* should be dependent on both libraries.  HP warns that the    * 
* result                                                       * 
* of mixing them includes unexpected failure.                  * 
*                                                              * 
*                                                              * 
*                                                              * 
* Although DB2 is built with the standard C++ library, it was  * 
*                                                              * 
* found that libdb2.so, the client side library of DB2, is     * 
* still                                                        * 
* linked with libstream.so, one of the classic C++ libraries.  * 
*                                                              * 
* Through the fix for this APAR, libstream.so will be removed. * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* Note that libdb2.so itself doesn't use any symbol from       * 
*                                                              * 
* libstream.so.  In other words, the warning posed by HP does  * 
* not                                                          * 
* apply to DB2 itself.                                         * 
*                                                              * 
*                                                              * 
*                                                              * 
* Important Note: If an application, which links with          * 
* libdb2.so,                                                   * 
* somehow references any symbol in the classic C++ library,    * 
* and if                                                       * 
* it had been accessing them via libdb2.so in the past, it     * 
* won't                                                        * 
* be able to access them after applying the fix for this APAR. * 
*                                                              * 
* The correct action is to fix the application to remove any   * 
*                                                              * 
* dependency on the classic C++ library.                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fixpack 3 or higher.                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 9.7 Fixpack 3. 
Assuming the customer's application is built correctly (i.e. no 
dependency on libstream.so), there will be no change.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC69784 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.07.2010
16.09.2010
16.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList