|
Problem IC69391
|
Status: Closed |
IMPROVE SQL5153N MESSAGE BY SHOWING WHAT THE <CONDITION> IS UNDE R WHEN A RESTORE FAILS DUE TO THIS MESSAGE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During a restore process, if restore was to fail with
SQL5153N message, the <condition> string for which the
relationship was violated is left NULL. Hence it makes it
difficult to diagnose why we got this message in the first
place.
.
For example:
.
SQL5153N The update cannot be completed because the following
relationship would be violated: "".
.
this apar will address this sort of situation and better log
messages in the db2diag.log and display the condition. |
| Problem Summary: |
During a restore process, if restore was to fail with
SQL5153N message, the <condition> string for which the
relationship was violated is left NULL. Hence it makes it
difficult to diagnose why we got this message in the first
place.
.
For example:
.
SQL5153N The update cannot be completed because the following
relationship would be violated: "".
.
this apar will address this sort of situation and better log
messages in the db2diag.log and display the condition. |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
apar fixed >= v97 fpk3 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC69627
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.06.2010
23.09.2010
23.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FPk3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
