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

A ONLINE backup using /INCLUDE/LOGS fails with SQL2428N and "Log could
not be retrieved" in the db2diag.log.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A backup, which includes log files, may fail if the log files 
that the backup needs are archived. Backup processing can 
timeout waiting for archived log files to be moved from the 
physical archive, if the files are large. 
 
You will come across the following error messages from the 
db2diag.log: 
 
2010-01-08-02.06.01.052413-300 I76730A364         LEVEL: Warning 
PID     : 123456               TID  : 1234        PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000 
EDUID   : 1234                 EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:4130 
MESSAGE : Started retrieve for log file S0000464.LOG. 
 
2010-01-08-02.06.11.592397-300 I77095A518         LEVEL: Error 
PID     : 123456               TID  : 1111      PROC : db2sysc 0 
INSTANCE: db2inst1               NODE : 000         DB   : 
SAMPLE 
APPHDL  : 0-12212              APPID: 
*LOCAL.db2inst1.100108021230 
AUTHID  : TESTUSER 
EDUID   : 1111               EDUNAME: db2bm.421213.20 (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpOpenLogForBackup, probe:20 
RETCODE : ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED 
          "Log could not be retrieved"
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The retrieval processing was not fast enough and the         * 
* backupprocessing assumes that the necessary log files will   * 
* beready but fails when it could not find one of the files.   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 2.                       * 
****************************************************************
Local-Fix:
Be sure that archived log files that the backup needs are 
available before the backup is attempted.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 9.7 Fix Pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66808 IC69324 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.01.2010
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList