|
Problem IC77149
|
Status: Closed |
After TAKEOVER, db2diag.log is filled with warning messages from functon hdrCheckDb. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When primary is switched to standby, all inflight transactions
including 'e' state (ended transactions) are rollbacked. But
ended expired transaction were not unregistered with the resync
process.
If application/TM sets transaction time out using
setTransactionTimeout jdbc
function or XATimeout (XT) variable in xaopen string (or CLI
keyword), the following messages can be
logged in db2diag.log in HADR system after TAKEOVER. These
messages are logged by db2sysc (resync process), which
tries to access the database (Now in standby mode) to rollback
expired ended ('e' state) transactions.
2011-06-01-17.00.06.422199+540 I9462838A507 LEVEL: Warning
PID : xxxx TID : xxxx PROC : db2sysc 0
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : x-xxxxx
EDUID : xxxxx EDUNAME: db2agent (xxx) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrCheckDb,
probe:18200
MESSAGE : Connections are not allowed on a standby database.
DATA #1 : Hexdump, 4 bytes
0x078000000158B8CC : FFFF F910
2011-06-01-17.00.06.423243+540 I9464649A471 LEVEL: Error
PID : xxxx TID : xxxx PROC : db2sysc 0
INSTANCE: db2 NODE : 000 DB : xxxxx
APPHDL : x-xxxx
EDUID : xxxx EDUNAME: db2agent (idle) 0
FUNCTION: DB2 UDB, DRDA Application Server, sqljs_ddm_syncrsy,
probe:50
MESSAGE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific
control
block."
The defect fix is to unregister ended expired transaction during
TAKEOVER process. The defect has no effect on the outcome of the
transaction. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 v9.7 FP 3a *
* AIX *
****************************************************************
* PROBLEM DESCRIPTION: *
* When primary is switched to standby, all inflight *
* transactions including 'e' state (ended transactions) are *
* rollbacked. But ended expired transaction were not *
* unregistered with the resync process. The message in *
* db2diag.log is logged when db2resync process tried to *
* rollback timedout or expired transactions. The defect fix is *
* to unregister ended expired transaction during TAKEOVER *
* process. *
****************************************************************
* RECOMMENDATION: *
* The defect fix is to unregister ended expired transaction *
* during TAKEOVER process. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
Problem First Fixed in DB2 Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.06.2011
12.02.2012
12.02.2012 |
| 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
|
 |
