|
Problem IT18383
|
Status: Closed |
SQL10007N MESSAGE "9517" COULD NOT BE RETRIEVED. REASON CODE: "4" ON HADR STANDBY |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
On the DB2 10.5 FP8 code you may observe on Standby messages
like:
2016-11-18-08.53.08.782494+060 E2081A488 LEVEL:
Warning
PID : 15975 TID : 4379952277776 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-8 APPID: *LOCAL.DB2.161118064949
HOSTNAME: hostname
EDUID : 288 EDUNAME: db2redom (SAMPLE) 0
FUNCTION: DB2 UDB, data management, sqldMarkObjInErr, probe:2
MESSAGE : SQL10007N Message "9517" could not be retrieved.
Reason code: "4".
Expected entry is similar to following:
ADM9517W The index object with ID "4" in table space "4" for
table
"TBSPACEID=3.TABLEID=4" has been marked invalid during log
replay on an HADR
standby database. The index will be rebuilt automatically upon
subsequent
query to this table, if there is a fail over to make this
database the HADR
primary.
This APAR change is to fix incorrect message. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.12.2016
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
