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

STANDBY MIGHT CRASH WITH SPOOLING ENABLED WITH "Unexpected extent
header received from the primary."

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The following db2diag.log message will appear before the standby 
crashes: 
 
2015-01-02-03.00.32.491181+000 I3499292E680          LEVEL: 
Error 
PID     : 37889                TID : 140736871786240 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-31                 APPID: *LOCAL.DB2.123456778787 
HOSTNAME: host1 
EDUID   : 64                   EDUNAME: db2shred (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:5750 
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
          DIA8526C A fatal error occurred in data protection 
services. 
DATA #1 : <preformatted> 
Unexpected extent header received from the primary. 
Received extent: 30079, Expected extent: 30080 - 30080 
 
2015-01-02-03.00.32.495476+000 I3499973E636          LEVEL: 
Error 
PID     : 37889                TID : 140736871786240 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-31                 APPID: *LOCAL.DB2.123456778787 
HOSTNAME: host1 
EDUID   : 64                   EDUNAME: db2shred (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:5750 
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
          DIA8526C A fatal error occurred in data protection 
services. 
DATA #1 : <preformatted> 
Error trying to extract log record 1226112883119 from log pages. 
 
[...] 
2015-01-02-03.00.32.748864+000 E3509194E990          LEVEL: 
Critical 
PID     : 37889                TID : 140699206936320 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-31                 APPID: *LOCAL.DB2.123456778787 
HOSTNAME: host1 
EDUID   : 113                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, base sys utilities, 
sqleDoForceDBShutdownFODC, probe:10 
MESSAGE : ADM14001C  An unexpected and critical error has 
occurred: 
          "ForceDBShutdown". The instance may have been shutdown 
as a result. 
          "Automatic" FODC (First Occurrence Data Capture) has 
been invoked and 
          diagnostic information has been recorded in directory 
 
"/local/home/db2inst1/sqllib/db2dump/FODC_ForceDBShutdown_2015-0 
1-02- 
          03.00.32.748727_0000/". Please look in this directory 
for detailed 
          evidence about what happened and contact IBM support 
if necessary to 
          diagnose the problem.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************
Local Fix:
Disable HADR log spooling
Solution
First fixed in Db2 10.5 Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.09.2016
29.09.2017
22.10.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)