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 IC84331 Status: Geschlossen

RESTORE FAILS DUE TO NOT BEING ABLE TO OPEN A LOG FILE IN SQLPGRML() PROBE
80

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
During database restore customer receives SQLP_BADLOG "Log File 
cannot be used" DIA8414C Logging can not continue due to an 
error in sqlpgrml() probe 80 
 
2011-06-23-17.30.48.215465-240 E52154A491         LEVEL: Info 
PID     : 1024016              TID  : 3345        PROC : db2sysc 
505 
INSTANCE: odsint               NODE : 505         DB   : ODSINT 
APPHDL  : 505-54               APPID: *N505.odsint.110623213032 
AUTHID  : ODSINT 
EDUID   : 3345                 EDUNAME: db2agent (ODSINT) 505 
FUNCTION: DB2 UDB, database utilities, sqludPrintStartingMsg, 
probe:1349 
DATA #1 : <preformatted> 
Starting a full database restore. 
Agent EDU ID: 3345 
: 
: 
 
and then we get the log file errors: 
 
2011-06-23-18.15.41.875326-240 I107399A513        LEVEL: Error 
PID     : 1724578              TID  : 3345        PROC : db2sysc 
88 
INSTANCE: odsint               NODE : 088         DB   : ODSINT 
APPHDL  : 88-54                APPID: *N88.odsint.110623213042 
AUTHID  : ODSINT 
EDUID   : 3345                 EDUNAME: db2agent (ODSINT) 88 
FUNCTION: DB2 UDB, data protection services, sqlpgolf, probe:570 
DATA #1 : <preformatted> 
FileName /udblogs/odsint/NODE0088/S0269612.LOG have extent 
headers with Chk1 0 and 0 
 
2011-06-23-18.15.41.880955-240 I107913A165        LEVEL: Warning 
PID:1724578 TID:3345 NODE:088 Title: SQLPG_XHDR 
Dump File:/udbdiag/odsint/1724578.3345.088.dump.bin 
 
2011-06-23-18.15.41.896601-240 I108079A165        LEVEL: Warning 
PID:1724578 TID:3345 NODE:088 Title: SQLPG_XHDR 
Dump File:/udbdiag/odsint/1724578.3345.088.dump.bin 
 
2011-06-23-18.15.41.906417-240 I108245A465        LEVEL: Error 
PID     : 1724578              TID  : 3345        PROC : db2sysc 
88 
INSTANCE: odsint               NODE : 088         DB   : ODSINT 
APPHDL  : 88-54                APPID: *N88.odsint.110623213042 
AUTHID  : ODSINT 
EDUID   : 3345                 EDUNAME: db2agent (ODSINT) 88 
FUNCTION: DB2 UDB, data protection services, sqlpgrml, probe:80 
MESSAGE : Error deleting logpath1: '/udblogs/odsint/NODE0088/' 
 
2011-06-23-18.15.41.911588-240 I108711A538        LEVEL: Error 
PID     : 1724578              TID  : 3345        PROC : db2sysc 
88 
INSTANCE: odsint               NODE : 088         DB   : ODSINT 
APPHDL  : 88-54                APPID: *N88.odsint.110623213042 
AUTHID  : ODSINT 
EDUID   : 3345                 EDUNAME: db2agent (ODSINT) 88 
FUNCTION: DB2 UDB, data protection services, sqlpgrml, probe:80 
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File 
cannot be used" 
          DIA8414C Logging can not continue due to an error.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.1 on LUW users.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 1 or higher.                   * 
****************************************************************
Local-Fix:
Delete (or move) all log files from the path referenced in the 
"sqlpgrml, probe 80" message, and try the restore again.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem fixed in DB2 V10.1 Fix Pack 1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
24.06.2013
24.06.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList