DB2 - Problem description
Problem IC77060 | Status: Closed |
REORG INDEX ON READ ENABLED HADR STANDBY COULD CAUSE KEY DATA MISMATCH | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In ROS(Reads On Standby) enabled HADR environment, running reorg index command on standby will get error messages in db2diag.log as shown below and later when Standby becomes Primary, index mismatch will occur and will lead to some unpredictable errors. 2011-04-18-07.37.25.845444-240 E274022578A546 LEVEL: Warning PID : 6693 TID : 62 PROC : db2sysc INSTANCE: DB2 NODE : 000 DB : HADRDB APPHDL : 0-34624 APPID: 9.26.97.92.52420.110418202048 AUTHID : DB2 EDUID : 62 EDUNAME: db2agent (HADRDB) FUNCTION: DB2 UDB, relation data serv, sqlrreorg_indexes, probe:400 MESSAGE : ADM9501W Index reorganization has started for table "HADR .TABLE13" (ID "6") and table space "TBSP_D32R" (ID "28"). 2011-04-18-07.37.25.848445-240 I274023125A553 LEVEL: Error PID : 6693 TID : 62 PROC : db2sysc INSTANCE: DB2 NODE : 000 DB : HADRDB APPHDL : 0-34624 APPID: 9.26.97.92.52420.110418202048 AUTHID : DB2 EDUID : 62 EDUNAME: db2agent (HADRDB) FUNCTION: DB2 UDB, relation data serv, sqlrr_write_ddlstart_lr, probe:100 RETCODE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY "The operation that attempted to modify the contents of the database failed" 2011-04-18-07.37.25.848614-240 I274023679A535 LEVEL: Error PID : 6693 TID : 62 PROC : db2sysc INSTANCE: DB2 NODE : 000 DB : HADRDB APPHDL : 0-34624 APPID: 9.26.97.92.52420.110418202048 AUTHID : DB2 EDUID : 62 EDUNAME: db2agent (HADRDB) FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:123 MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY "The operation that attempted to modify the contents of the database failed" 2011-04-18-07.37.25.858360-240 I274024215A535 LEVEL: Error PID : 6693 TID : 62 PROC : db2sysc INSTANCE: DB2 NODE : 000 DB : HADRDB APPHDL : 0-34624 APPID: 9.26.97.92.52420.110418202048 AUTHID : DB2 EDUID : 62 EDUNAME: db2agent (HADRDB) FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:123 MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY "The operation that attempted to modify the contents of the database failed" 2011-04-18-07.37.25.858513-240 I274024751A548 LEVEL: Severe PID : 6693 TID : 62 PROC : db2sysc INSTANCE: DB2 NODE : 000 DB : HADRDB APPHDL : 0-34624 APPID: 9.26.97.92.52420.110418202048 AUTHID : DB2 EDUID : 62 EDUNAME: db2agent (HADRDB) FUNCTION: DB2 UDB, data management, sqldBeginIndexCreate, probe:515 RETCODE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY "The operation that attempted to modify the contents of the database failed" Upon receiving error messages above, if indexes are getting updated on primary and takeover is run on standby, and then when accessing those indexes on new primary, DB2 will throw error message as follows. DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0901N The SQL statement failed because of a non severe system error. Subsequent SQL statements can be processed. (Reason "Key data mismatch encountered during key update".) SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * hadr users on all platforms * **************************************************************** * PROBLEM DESCRIPTION: * * without the fix, customer could hit the problem described in * * error description * **************************************************************** * RECOMMENDATION: * * upgrade to db2 v97fp5 * **************************************************************** | |
Local Fix: | |
reorg index on new primary after takeover succeeds | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
the fix is in v97fp5. With the fix, reorg index on standby could not cause index data mismatch | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.06.2011 07.12.2011 07.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |