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 IC78442 Status: Geschlossen

"EXPORT DB2LIBPATH " FROM DB2PROFILE CAUSES LIBPATH BROKEN.

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
Command "export DB2LIBPATH" is executed from db2profile to point 
to ${jdkpath?}/jre/lib/ppc64 in response to a JDK update on AIX. 
However, this value will override the DB2LIBPATH set at 
instance level. 
 
$ db2set -all 
[e] DB2LIBPATH=/opt/IBM/sqllib/java/jdk64/jre/lib/ppc64 
[i] DB2LIBPATH=/mydirectory/lib 
 
With above entries, /mydirectory/lib will be overriden which 
leads to "library not found" error SQL0444 rc=4 for routines.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all AIX users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Any value of DB2LIBPATH set via db2set will be ignored.      * 
* This normally results in libraries not being found at        * 
* runtime for stored procedures or other user extensions to    * 
* DB2.                                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 v9.8 Fixpack 4.                                * 
****************************************************************
Local-Fix:
Manually run "export DB2LIBPATH=/mydirectory/lib" and recycle 
instance.
Lösung
Fixed in DB2 v9.8 Fixpack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.09.2011
15.09.2011
15.09.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP4
Problem behoben lt. FixList in der Version