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

HADR STANDBY MIGHT GET CORRUPTED IN CASE FAILURE DURING MULTIPLEREORG
RUNNING ON HADR PRIMARY

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
During multiple REORG operations running on the HADR Primary,
the Standby database might get corrupted in case of unexpected
shutdown on the Standby. Once this happens, user will observe
following messages on Standby during DB activation:

2016-05-24-15.40.24.794779+120 I536037A499          LEVEL: Event

PID     : 21978                TID : 4390870051088  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000           DB   : TEST

APPHDL  : 0-11                 APPID: *LOCAL.DB2.160524134024

HOSTNAME: node01

EDUID   : 288                  EDUNAME: db2redom (TEST) 0

FUNCTION: DB2 UDB, data management, sqldObtainReorgTemp,
probe:2227
CHANGE  : Tablespace 39 is already reserved. poolReorgCount = 3.
LSN =
0000062A1D7FC031.



2016-05-24-15.40.24.816948+120 I536537A545          LEVEL: Error

PID     : 21978                TID : 4390870051088  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000           DB   : TEST

APPHDL  : 0-11                 APPID: *LOCAL.DB2.160524134024

HOSTNAME: node01

EDUID   : 288                  EDUNAME: db2redom (TEST) 0

FUNCTION: DB2 UDB, buffer pool services, sqlbResv4Reorg,
probe:2046
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error
detected"

          DIA8501C A buffer pool logic error has occurred.

...

2016-05-24-15.40.26.426091+120 I581323A562          LEVEL: Error

PID     : 21978                TID : 4395500562704  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000           DB   : TEST

HOSTNAME: node01

EDUID   : 558                  EDUNAME: db2hadrs.0.0 (TEST) 0

FUNCTION: DB2 UDB, data protection services,

sqlpgPostLoggrWithoutLatching, probe:930

MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
cannot be
used"

          DIA8414C Logging can not continue due to an error.

DATA #1 : 

db2logger: sem rc=0 type=5



...


2016-05-24-15.40.31.621563+120 I588302A570          LEVEL:
Severe
PID     : 21978                TID : 4395584448784  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000           DB   : TEST

APPHDL  : 0-12                 APPID: *LOCAL.DB2.160524134025

HOSTNAME: node01

EDUID   : 20                   EDUNAME: db2agent (TEST) 0

FUNCTION: DB2 UDB, base sys utilities,
sqeApplication::AppStopUsing,
probe:7076

MESSAGE : ZRC=0xFFFFFBF6=-1034

          SQL1034C  The database was damaged, so all
applications
processing the database were stopped.



The stack for that call looks like this (below is from traces):

sqeDBMgr::StartUsingLocalDatabase entry [eduid 294 eduname
db2agent]
| sqeLocalDatabase::FirstConnect entry [eduid 294 eduname
db2agent]
| | sqledint entry [eduid 294 eduname db2agent]
| | | sqlbinit entry [eduid 294 eduname db2agent]
| | | | sqlbStartPools entry [eduid 294 eduname db2agent]
| | | | | sqlbSMSStartPool entry [eduid 294 eduname db2agent]
| | | | | | sqlbSMSDoContainerOp entry [eduid 294 eduname
db2agent]
| | | | | | | sqlbSMSScanTagFile entry [eduid 294 eduname
db2agent]
| | | | | | | | sqlbContainerTagIsValid entry [eduid 294 eduname



Reason for the error is incorrectly processed internal
structures which manifests in error above.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 11.1 Mod2 Fix Pack 2 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT16538 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.10.2017
27.10.2017
27.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)