|
Problem IC67045
|
Status: Geschlossen |
A DATABASE WITH CIRCULAR LOGGING CAN FAIL IN CRASH RECOVERY TRYING TO OPEN LOG FILES THAT DO NOT EXIST ON DISK |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
Crash recovery can incorrectly fail on a database with Circular
logging if the Log Control File ( SQLOGCTL.LFH.1/2 )
has more pre-allocated, but unused, log files registered than
what physically exists in the Active Log Directory.
The db2diag.log may show the following messages during Crash
Recovery :
2010-03-04-22.46.39.425929+060 I59656006E429 LEVEL: Error
PID : 7918 TID : 47211861764416PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 44 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgicl,
probe:2130
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "S0000058.LOG" could not be found.
2010-03-04-22.46.39.426554+060 I59656436E423 LEVEL: Error
PID : 7918 TID : 47211861764416PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 44 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgLoggrInit,
probe:1150
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
Local Fix : Upgrade to a version that fixes this problem in
order to let crash recovery complete, or contact DB2 Support in
order to manually patch the Log Control File to circumvent the
problem. |
| Problem-Zusammenfassung: |
A DATABASE WITH CIRCULAR LOGGING CAN FAIL IN CRASH RECOVERY
TRYING TO OPEN LOG FILES THAT DO NOT EXIST ON DISK |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
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 |
Problem was first fixed in Version 9.5 Fix Pack 6 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC67126 IC68138
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 10.03.2010
17.05.2010
17.05.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP6
|
| Problem behoben lt. FixList in der Version |
