|
Problem IC78442
|
Status: Closed |
"EXPORT DB2LIBPATH " FROM DB2PROFILE CAUSES LIBPATH BROKEN. |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| Solution |
Fixed in DB2 v9.8 Fixpack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.09.2011
15.09.2011
15.09.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
