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 IT18839 Status: Closed

FATAL ERROR WHEN TAKING MULTIPLE SNAPSHOT BACKUPS WITH NO TRANSACTION(S) IN
BETWEEN

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Doing repeated offline snapshot backup/restore/rollforward 
cycles happen with no 
transactions in between will lead to fatal error. 
The db2diag message might look like: 
 
2016-10-13-21.36.55.218465+120 I171860A2060         LEVEL: Error 
PID     : 33751078             TID : 3857           PROC : 
db2sysc 1 
INSTANCE: db2db1               NODE : 001           DB   : DB1 
APPHDL  : 0-57                 APPID: *N0.db2db1.161013193652 
AUTHID  : DB2DB1               HOSTNAME: hostname 
EDUID   : 3857                 EDUNAME: db2agntp (DB1) 1 
FUNCTION: DB2 UDB, recovery manager, sqlpAddGTruncPoint, 
probe:6130 
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
          DIA8526C A fatal error occurred in data protection 
services. 
DATA #1 : String, 54 bytes 
Cannot have 2 entries in GTA with same LFS/LSN values. 
DATA #2 : SQLP_GLOBAL_LOG_POS, PD_TYPE_SQLP_GLOBAL_LOG_POS, 24 
bytes 
45 0000000000000069 1476387415 14302 
DATA #3 : Global Truncation Array, PD_TYPE_SQLP_GTA, 728 bytes 
idx                    Lfs              Lsn  ChainTime 
Signature 
  0                      0 0000000000000000 1460624207 
18112 
  1                     24 0000000000000027 1475834047 
26341 
  2                     40 000000000000005F 1476185922 
11036 
  3                     45 0000000000000069 1476387224 
27470 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved 
to the nearest symbol) 
  [0] 0x090000001CBD6D4C 
sqlpAddGTruncPoint__FP18SQLP_G_TRUNC_ARRAYPC19SQLP_GLOB 
AL_LOG_POSP15sqlpDbcbsHandle + 0x3E8 
  [1] 0x090000001CCB5294 
sqlpAddGTruncPoint__FP15sqlpDbcbsHandlePC19SQLP_GLOBAL_ 
LOG_POS + 0x528 
  [2] 0x090000001CE28434 
sqlpForwardRecovery__FP8sqeAgentUsPCcPiPUiT2 + 0x1379C 
  [3] 0x090000001CE5CB18 sqlpPdbRfwRouter__FP8sqeAgent + 0x21E4 
  [4] 0x090000001CE52B18 sqlpPdbRfwRouter__FP8sqeAgent + 0xEA0 
  [5] 0x09000000191C8568 
@82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x200C 
  [6] 0x090000001BB2558C RunEDU__8sqeAgentFv + 0x35A4C 
  [7] 0x090000001BAA5738 RunEDU__8sqeAgentFv + 0x124 
  [8] 0x090000001A8BAAE4 EDUDriver__9sqzEDUObjFv + 0x130 
  [9] 0x090000001A54C2D4 sqloEDUEntry + 0x3A0 
  [10] 0x09000000004CAE10 _pthread_body + 0xF0 
  [11] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
 
2016-10-13-21.36.55.219121+120 I173921A572          LEVEL: Error 
PID     : 33751078             TID : 3857           PROC : 
db2sysc 1 
INSTANCE: db2db1               NODE : 001           DB   : DB1 
APPHDL  : 0-57                 APPID: *N0.db2db1.161013193652 
AUTHID  : DB2DB1               HOSTNAME: hostname 
EDUID   : 3857                 EDUNAME: db2agntp (DB1) 1 
FUNCTION: DB2 UDB, recovery manager, sqlpAddGTruncPoint, 
probe:6115 
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
          DIA8526C A fatal error occurred in data protection 
services.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 8                               * 
****************************************************************
Local Fix:
Avoid taking multiple snapshot backups with no transaction(s) in 
between or do some transaction(s) between multiple snapshot 
backups.
Solution
First Fixed in DB2 10.5 Fix Pack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.01.2017
16.08.2017
16.08.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)