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

HADR STANDBY FAILED TO START WITH ERROR SQLD_PRGERR

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
HADR standby fails to start because of a SQLD_PRGERR error in 
function reInitShadowInxInfo.  The error is raised when 
replaying log records for a REORG INDEXES operation. 
 
If this problem is hit, the following entry will appear in the 
db2diag.log: 
 
2012-04-05-05.50.02.684888-240 I60751E529          LEVEL: Severe 
PID     : 25629                TID  : 469129085525 PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000          DB   : 
SAMPLEDB 
APPHDL  : 0-13                 APPID: *LOCAL.DB2.120405094622 
EDUID   : 41                   EDUNAME: db2redom (SAMPLEDB) 
FUNCTION: DB2 UDB, data management, reInitShadowInxInfo, 
probe:3758 
RETCODE : ZRC=0x87040055=-2029780907=SQLD_PRGERR "Unknown 
PROGRAM ERROR" 
          DIA8576C A data management services programming error 
occurred.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See APAR IC82667                                             * 
****************************************************************
Local Fix:
To avoid hitting the problem: 
- Set the database configuration parameter LogIndexBuild to Off 
OR 
- Put the indexes in the same tablespace as the parent table OR 
- Avoid running REORG INDEXES on tables that have their indexes 
in a different tablespace
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.12.2013
11.05.2017
11.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)