IBM Support

IC77060: REORG INDEX ON READ ENABLED HADR STANDBY COULD CAUSE KEY DATA MISMATCH

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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
    

Local fix

  • reorg index  on new primary after takeover succeeds
    

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                                        *
    ****************************************************************
    

Problem conclusion

  • the fix is in v97fp5. With the fix, reorg index on standby could
    not cause index data mismatch
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77060

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-20

  • Closed date

    2011-12-07

  • Last modified date

    2011-12-07

  • 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 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC77060

Modified date: 07 December 2011