|
Problem IC69321
|
Status: Geschlossen |
ABEND ON HADR PRIMARY DUE TO BADLOG ERROR IN SQLPGWRITETODISK |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
A HADR primary database can fail with the following message :
EDUID : 23 EDUNAME: db2loggw (SAMPLE)
FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk,
probe:909
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
cannot be used"
DIA8414C Logging can not continue due to an error.
DATA #1 : <preformatted>
TailPage 0 does not match pagelsn 0015AD388052 and firstlsn
0015AE388000
This is typically seen after a non forced takeover and when
mirrored logging is enabled. ( mirrorlogpath set in the db cfg
).
Another eyecatcher is the following error that may happen some
time prior to this during the takeover :
2010-06-17-15.55.59.401076+120 I125515E447 LEVEL: Severe
PID : 21100 TID : 183236553056 PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000
EDUID : 39 EDUNAME: db2hadrs (SAMPLE)
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrAddLogFiles, probe:10150
RETCODE : ZRC=0x071000E3=118489315=SQLP_RETRY_GADF
"sqlpgCallGIFL: block on log disk. sqlpgReuseCAL: log file
deleted" |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* HADR environments *
****************************************************************
* PROBLEM DESCRIPTION: *
* A DB2 primary database may abend under specific *
* conditionswhen log mirroring is enabled. *
****************************************************************
* RECOMMENDATION: *
* Upgrade the database server to DB2 v9.5 Fixpak 7 *
**************************************************************** |
| Local-Fix: |
The primary database recovers from this after a database
restart. |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
This problem was first fixed in V9.5 Fixpak 7 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC70431 IC70432
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 17.06.2010
15.11.2010
15.11.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
