invispix 10x10
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 IT39049 Status: Closed

AFTER HADR UPGRADE AND THEN TAKEOVER FROM STANDBY, LOG WRITES ONNEW
PRIMARY CAN CAUSE FORCEDBSHUTDOWN.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
After HADR Upgrade (without standby re-initialization) and
immediately issue takeover from standby, log writes on new
primary can cause ForceDbShutdown.

In db2diag.log:
2016-09-19-21.34.35.145946-240 I3063656A1996        LEVEL: Error
PID     : 10813672             TID : 42174          PROC :
db2sysc 0
INSTANCE: db2instance      NODE : 000           DB   : MYDB1
APPHDL  : 0-169                APPID: *N0.DB2.160920013431
AUTHID  : DB2INSTANCE    HOSTNAME: hadrhost2
EDUID   : 42174                EDUNAME: db2agent (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpWriteLR,
probe:3943
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
Error"
          DIA8526C A fatal error occurred in data protection
services.
DATA #1 : 
Unexpected condition!!! Call sequence error -- Log records
written before database migration begins.
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x090000002679ED68 pdLogPrintf + 0x28
  [1] 0x0900000027DFE77C
sqlpWriteLR__FP8sqeAgentUlN42P14SQLP_LREC_PARTT2P9SQLP_LSN8PUl +
0x45C
  [2] 0x0900000028EBFD14 sqlrr_write_ddlstart_lr__FP8sqlrr_cb +
0x394
  [3] 0x0900000028A02B48
sqldBeginIndexCreate__FP8sqeAgentP17SQLD_CREATEINX_CB + 0x58E8
  [4] 0x0900000028E02B30
sqlrlRecreateIndexObject__FP8sqlrr_cbP8sqlrg_idP17SQLD_CREATEINX
_CBUiUsUlP25sqlyk_keyXform_threadListP23SqlthJobProgressMonit
or + 0xB0
  [5] 0x0900000028E05DA4
sqlrlRecreateIndexes__FP8sqlrr_cbUsT2P8sqlrg_idiPUcT5T6T5UiPsUcP
8SqlthJobT2P9SQLP_LSN8T2P14SQLP_LOCK_INFOT6 + 0x8A4
  [6] 0x0900000028E099E0
sqlrlCheckIndex__FP8sqlrr_cbUsT2P8sqlrg_idiPUcT5T6T5UiUcPsT10_P8
SqlthJob + 0x500
  [7] 0x0900000028E0C090
sqlrlrci_all_rt__FP8sqlrr_cbsP15SQLR_RPCMESSAGEN22UiPs + 0x1790
  [8] 0x0900000028E0CAAC sqlrlrci_all__FP8sqlrr_cbsT2P5sqlca +
0x74C
  [9] 0x0900000029756068 sqleIndCoordProcessRequest__FP8sqeAgent
+ 0x988
  [10] 0x09000000269526E8 RunEDU__8sqeAgentFv + 0xAA8
  [11] 0x09000000269352A0 EDUDriver__9sqzEDUObjFv + 0x2E0
  [12] 0x0900000026826794 sqloEDUEntry + 0x374
  [13] 0x0900000000541E10 _pthread_body + 0xF0
  [14] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* HADR users                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fix pack                               *
****************************************************************
Local Fix:
Reactivate the new primary.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* HADR users                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fix pack                               *
****************************************************************
Comment
Problem was first fixed in DB2 LUW VERSION 11.1 Mod 1 Fixpack 1
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.11.2021
24.01.2022
03.04.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
invispix 10x10
invispix 10x10
Versions InfomailVersions Infomail

Versions Infomail

Product LifecycleProduct Lifecycle

Lifecycle

Current BugsCurrent Bugs

Current Bugs

Bug ResearchBug Research

Bug Research

Bug FixlistsBug Fixlists

Bug Fixlists

invispix 10x10