|
Problem IC93243
|
Status: Closed |
IN HADR ENVIRONMENT, AFTER SEVERAL TAKEOVERS, DB2 PRIMARY MAY GET PANIC DUE TO THE LOG FULL ISSUE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In HADR environment, after several takeovers, db2 primary may
get panic due to the log full issue.
This issue could be triggered by the following conditions:
1. do take over 2-3 times without active transactions
2. after takeover, there is a 'long' transaction that holding
the First Active Log on primary
When the issue happened, the following entry will be written
into db2diag.log:
2013-05-13-02.15.09.651179+480 E289476622A586 LEVEL: Severe
PID : 4653424 TID : 5535 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 5535 EDUNAME: db2loggw (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk,
probe:1010
MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
"Log File has reached its saturation point"
DIA8309C Log file was full.
DATA #1 : <preformatted>
Error getting next log file to write to. Filecount 40, active
40, inactive 190, tailindex 39 currentRecord 67337
also during take over, you can see message as below:
2013-06-13-21.38.00.705305-420 I913017E404 LEVEL: Info
PID : 25011 TID : 46912942106944PROC :
db2sysc
INSTANCE: sample NODE : 000 DB :
SAMPLE
EDUID : 123 EDUNAME: db2loggr (SAMPLE)
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo,
probe:1790
DATA #1 : <preformatted>
Reused last log 14, FileCount is 1, TailIndex is 0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* In HADR environment, after several takeovers, db2 primary *
* may *
* get panic due to the log full issue. *
* *
* This issue could be triggered by the following conditions: *
* *
* 1. do take over 2-3 times without active transactions *
* *
* 2. after takeover, there is a 'long' transaction that *
* holding *
* the First Active Log on primary *
* *
* When the issue happened, the following entry will be written *
* into db2diag.log: *
* *
* 2013-05-13-02.15.09.651179+480 E289476622A586 LEVEL: *
* Severe *
* PID : 4653424 TID : 5535 PROC : *
* db2sysc *
* 0 *
* INSTANCE: db2inst1 NODE : 000 *
* EDUID : 5535 EDUNAME: db2loggw (SAMPLE) 0 *
* FUNCTION: DB2 UDB, data protection services, *
* sqlpgWriteToDisk, *
* probe:1010 *
* MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE *
* "Log File has reached its saturation point" *
* DIA8309C Log file was full. *
* DATA #1 : <preformatted> *
* Error getting next log file to write to. Filecount 40, *
* active *
* 40, inactive 190, tailindex 39 currentRecord 67337 *
* *
* *
* also during take over, you can see message as below: *
* *
* 2013-06-13-21.38.00.705305-420 I913017E404 LEVEL: *
* Info *
* PID : 25011 TID : 46912942106944PROC : *
* db2sysc *
* INSTANCE: sample NODE : 000 DB : *
* SAMPLE *
* EDUID : 123 EDUNAME: db2loggr (SAMPLE) *
* FUNCTION: DB2 UDB, recovery manager, *
* sqlpgSwitchFromRedoToUndo, *
* probe:1790 *
* DATA #1 : <preformatted> *
* Reused last log 14, FileCount is 1, TailIndex is 0 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v97fp9 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
The fix will be included db2_v97fp9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.06.2013
17.12.2013
17.12.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.9
|
 |
| 9.7.0.9
|
|
