home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC88339 Status: Closed

LOG RETRIEVAL DOES NOT CHECK THE FORMAT VERSION AND CAN CAUSE ERROR DURING
LATER CHECKING

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When database starts retrieval of log we do not check the Format 
Version to make sure it is the same as the current. 
 
This can result in various error when we try and check the size 
of the log or further along, due to mismatch in the structures. 
 
The tool db2cklog should also check for this. 
 
db2diag.log: 
 
2012-04-19-12.45.30.158090+120 I134579A369        LEVEL: Warning 
PID     : 495636               TID  : 2571        PROC : db2sysc 
0 
INSTANCE: db2inst1 NODE : 000 
EDUID   : 2571                 EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:4130 
MESSAGE : Started retrieve for log file S0005686.LOG. 
 
2012-04-19-12.45.32.422286+120 E134949A611        LEVEL: Error 
PID     : 495636               TID  : 2571        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 2571                 EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogVendor, probe:2516 
DATA #1 : String, 107 bytes 
The actual log file size did not match the expected file size, 
retrying retrieve. Actual / Expected / File: 
DATA #2 : signed integer, 8 bytes 
1245184 
DATA #3 : signed integer, 8 bytes 
8192 
DATA #4 : String, 51 bytes 
/ap/fh/fhdba03/fh0310bh/sqlog/NODE0000/S0005686.TMP 
 
2012-04-19-12.45.32.422678+120 E135561A562        LEVEL: Error 
PID     : 495636               TID  : 2571        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 2571                 EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogVendor, probe:2533 
MESSAGE : ZRC=0x870F000A=-2029060086=SQLO_FEXS "file already 
exists" 
          DIA8722C A file already exists. 
DATA #1 : String, 107 bytes 
An error was encountered moving the mismatched sized logfile to 
a saved file on the first retrieve attempt. 
 
2012-04-19-12.45.32.422976+120 I136124A606        LEVEL: Warning 
PID     : 495636               TID  : 2571        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 2571                 EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogVendor, probe:2697 
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
          DIA8526C A fatal error occurred in data protection 
services. 
DATA #1 : String, 84 bytes 
An error was encountered in first retrieve attempt. Retry will 
be attempted.  errId: 
DATA #2 : signed integer, 8 bytes 
3778
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 Fixpack 2 or higher                         * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
First Fixed in v10.1 Fixpack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2012
09.01.2013
09.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList