Fixes are available
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 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 10 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
When using the IBM DB2 Driver for JDBC and SQLJ, the driver will not function correctly if the datasource properties currentFunctionPath and currentPackagePath are used in conjunction with each other. The driver currently flows currentFunctionPath before currentPackagePath. If the packages used by set currentFunctionPath are unbound, an SQLCODE -805 error is thrown while executing the SET CURRENT PATH special register. Seting currentPackagePath will not fix the -805 problem because it is set after currentFunctionPath. This issue will also lead to SQLCODE -440 on calling stored procedures with unspecified (implicit) schema. To fix this problem, the driver will, in future releases, flow currentPackagePath first, so that the package path will apply to the following currentFunctionPath.
Local fix
Problem summary
When using the IBM DB2 Driver for JDBC and SQLJ, the driver will not function correctly if the datasource properties 'currentFunctionPath' and 'currentPackagePath' are used in conjunction with each other. The driver currently flows currentFunctionPath before currentPackagePath. If the packages used by set currentFunctionPath are unbound, an SQLCODE -805 error is thrown while executing the SET CURRENT PATH special register. Seting currentPackagePath will not fix the -805 problem because it is set after currentFunctionPath. This issue will also lead to SQLCODE -440 on calling stored procedures with unspecified (implicit) schema.
Problem conclusion
To fix this problem, the driver will, in future releases, flow currentPackagePath first, so that the package path will apply to the following currentFunctionPath.
Temporary fix
Comments
APAR Information
APAR number
LI74705
Reported component name
DB2 UDE ESE LIN
Reported component ID
5765F4104
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-23
Closed date
2010-08-31
Last modified date
2010-08-31
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
DB2 UDE ESE LIN
Fixed component ID
5765F4104
Applicable component levels
R950 PSY
UP
Document Information
Modified date:
31 August 2010