home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC68546 Status: Geschlossen

ROLLFORWARD COMMAND FAILED WITH SQL4970N ERROR

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When DB2 rollforward command with stop option is issued the 
requried log file was not found. Rollforwad command can't make 
the database consistent. failed with SQL4970N error. There is 
extra logic involved that ends up creating a new copy of 
required log file. The following messsgae could be db2diag.log 
file 
2010-03-23-23.15.34.375576-240 I4028087E420        LEVEL: Info 
PID     : 12262                TID  : 183278496096 PROC : 
db2sysc 3 
INSTANCE: DB2INST1             NODE : 003          DB   : SAMPLE 
EDUID   : 34412                EDUNAME: db2loggr (RAVESTAG) 3 
FUNCTION: DB2 UDB, data protection services, sqlpgCallGIFL, 
probe:1250 
DATA #1 : <preformatted> 
New log extent 50800, PId 1269236666, StartLsn 000008D5F5014000
Problem-Zusammenfassung:
When DB2 rollforward command with stop option is issued the 
 
requried log file was not found. Rollforwad command can't make 
the database consistent. failed with SQL4970N error. There is 
extra logic involved that ends up creating a new copy of 
required log file. The following messsgae could be db2diag.log 
file 
2010-03-23-23.15.34.375576-240 I4028087E420        LEVEL: Info 
PID     : 12262                TID  : 183278496096 PROC : 
db2sysc 3 
INSTANCE: DB2INST1             NODE : 003          DB   : SAMPLE 
EDUID   : 34412                EDUNAME: db2loggr (RAVESTAG) 3 
FUNCTION: DB2 UDB, data protection services, sqlpgCallGIFL, 
probe:1250 
DATA #1 : <preformatted> 
New log extent 50800, PId 1269236666, StartLsn 000008D5F5014000
Local-Fix:
Make sure all the requried log file available. Especially when 
the overflow log path is used for rollward. The following 
command is recommened: rollforward db <dbname> stop overflow log 
path (xxXX)
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
The APAR is first fixed in DB2 v9.7fp3
Workaround
Make sure all the requried log file available. Especially when 
the overflow log path is used for rollward. The following 
command is recommened: rollforward db <dbname> stop overflow log 
path (xxXX)
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.05.2010
23.09.2010
23.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList