DB2 - Problem description
| Problem IT05225 | Status: Closed |
IMPORT AND EXPORT RETURNS INCORRECT SQL3015N WHEN REBIND PACKAGE FAILS | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
In the import and export utilities, there are numerous places where the utilities attempt to automatically rebind packages if necessary. If the rebind attempt fails, an SQLCODE -3015 error may be returned. The utilities should return SQLCODE -2019 instead. (This behaviour affects QReplication logic, which expects SQLCODE -2019 for such errors.) | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * IMPORT/EXPORT users upgrading to DB2 10.5 fix pack 4 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 fix pack 5. * **************************************************************** | |
| Local Fix: | |
Manually bind/rebind db2ubind.lst after upgrading to new fix pack. | |
| Solution | |
The problem is fixed in DB2 10.5 fix pack 5. | |
| Workaround | |
see Local Fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.10.2014 06.02.2015 06.02.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.5 |
|