|
Problem IC68210
|
Status: Geschlossen |
CRASH RECOVERY FAILED WITH -1042 ERROR WHICH MARKED THE DB BAD. IT FAILED WITH "FILE COUNT <= TAILINDEX" ERROR IN DB2DIAG.LOG. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
Crash recovery failes with -1042 error marking the db bad. This
is caused
due to crash recovery completing too early thus calculating the
tailindex wrongly. The crash recovery ended early due to logs
being unavailable during the crash recovery.
db2diag.log entries look like this:
2010-01-19-01.39.02.173625-120 I710234A341 LEVEL: Error
PID : 381160 TID : 3343 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 3343 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo,
probe:1820
MESSAGE : File Count <= TailIndex
2010-01-19-01.39.02.173888-120 I710576A166 LEVEL: Error
PID:381160 TID:3343 NODE:000 Title: SQLP_DBCB
Dump File:/db2logs/DIAG/db2inst1/381160.3343.000.dump.bin
2010-01-19-01.39.02.184985-120 I710743A435 LEVEL: Error
PID : 381160 TID : 3343 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 3343 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgasn, probe:650
RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
Error"
DIA8526C A fatal error occurred in data protection
services.
2010-01-19-01.39.02.201262-120 I711179A478 LEVEL: Error
PID : 381160 TID : 7712 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-7 APPID:
*LOCAL.db2inst1.100119033834
AUTHID : db2inst1
EDUID : 7712 EDUNAME: db2redom (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgPostLoggrWithoutLatching, probe:930
MESSAGE : db2logger: rc=-2028994531 sem rc=0 type=28
With this APAR fix, we will detect the failure and shut down
cleanly, making it possible to correct the failure (make the
file available) and re-issue the recovery. |
| Problem-Zusammenfassung: |
CRASH RECOVERY FAILED WITH -1042 ERROR WHICH MARKED THE DB BAD.
IT FAILED WITH "FILE COUNT <= TAILINDEX" ERROR IN DB2DIAG.LOG. |
| Local-Fix: |
Make sure all the transaction files needed for crash recovery
are available and re-issue the crash recovery by restarting db2. |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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
|
| Lösung |
Fixed in DB2 V97FP3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 28.04.2010
29.09.2010
29.09.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP3
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
