Instance may crash with error (in db2diag.log): "rollout CB list
is not empty at tx boundary!"
The following error is an example of the db2diag.log error
message that will be logged if the problem is hit.
2013-09-26-15.52.17.576894+000 I513090117A1400 LEVEL: Error
PID : 3801168 TID : 60654 PROC : db2sysc 0
INSTANCE: db2bp1 NODE : 000 DB : BP1
APPHDL : 0-229 APPID: 10.6.220.39.33750.1309151
AUTHID : DB2BP1
EDUID : 60654 EDUNAME: db2agent (BP1) 0
FUNCTION: DB2 UDB, sqldb, sqldb_purgeAllRolloutCBsFromTENTRY,
probe:581
MESSAGE : Rollout CB list is not empty at tx boundary!
DATA #1 : Pointer, 8 bytes
0x0a00020ee19cdb20
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000012755FB0 pdLog + 0xE0
[1] 0x090000000F7AD758
sqldb_purgeAllRolloutCBsFromTENTRY__FP8sqeAgent + 0x1E8
[2] 0x0900000012645AA8
sqlpEndUowRuntime__FP8sqeAgentP9SQLP_DBCB + 0x4
[3] 0x09000000124DF058 @108@sqlpAbortProcessing__FP8sqeAgentUi
+ 0x5C
[4] 0x09000000124DEC44
sqlpxrbk__FP8sqeAgentP15SQLXA_CALL_INFOPiP9SQLP_GXIDPP11sqlo_xla
tch + 0x45C
[5] 0x09000000124DF588
sqlrrbck_dps__FP8sqlrr_cbiN22P15SQLXA_CALL_INFOP9SQLP_GXIDb +
0x1A4
[6] 0x09000000124E0E44
sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO + 0x17C
[7] 0x09000000124E0088 sqlrr_rollback__FP14db2UCinterface +
0xE0
[8] 0x09000000124DFF1C
sqljs_ddm_rdbrllbck__FP14db2UCinterfaceP13sqljDDMObject + 0x144
[9] 0x09000000124DFD00
sqljs_ddm_rdbrllbck__FP14db2UCinterfaceP13sqljDDMObject@glue179D
+ 0x74
2013-09-26-15.52.17.579351+000 I513091518A587 LEVEL: Error
PID : 3801168 TID : 60654 PROC : db2sysc 0
INSTANCE: db2bp1 NODE : 000 DB : BP1
APPHDL : 0-229 APPID: 10.6.220.39.33750.1309151
AUTHID : DB2BP1
EDUID : 60654 EDUNAME: db2agent (BP1) 0
FUNCTION: DB2 UDB, data protection services, sqlpEndUowRuntime,
probe:750
RETCODE : ZRC=0x870400CC=-2029780788=SQLDB_PRGERR
"Block Management Services program error"
DIA8737C A block management services programming error
occurred.
The problem might occur when the following criteria are met:
1) The table is an MDC table with at least one RID index.
2) A deferred cleanup rollout delete is performed on that MDC
table. The conditions that need to be met for a delete to be
classified as a rollout delete are:
- The DELETE statement is a searched DELETE, not a positioned
DELETE (the statement does not use the WHERE CURRENT OF clause).
- There is no WHERE clause (all rows are to be deleted), or
the only conditions in the WHERE clause apply to dimensions.
- The table is not defined with the DATA CAPTURE CHANGES
clause.
- The table is not the parent in a referential integrity
relationship.
- The table does not have ON DELETE triggers defined.
- The table is not used in any MQTs that are refreshed
immediately.
- A cascaded delete operation might qualify for rollout if
its foreign key is a subset of the table's dimension columns.
- The DELETE statement cannot appear in a SELECT statement
executing against the temporary table that identifies the set of
affected rows prior to a triggering SQL operation (specified by
the OLD TABLE AS clause on the CREATE TRIGGER statement).
The default behavior, immediate cleanup rollout, is to clean
up RID indexes during the time of deletion. A deferred cleanup
rollout delete is used when the user sets the DB2_MDC_ROLLOUT
registry variable to DEFER, or by specifying DEFERRED on the SET
CURRENT MDC ROLLOUT MODE statement.
3) The transaction containing the deferred cleanup rollout
delete is rolled back. |
