home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98043 Status: Geschlossen

HADR STANDBY FAILED TO START WITH ERROR SQLD_PRGERR

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.12.2013
11.05.2017
11.05.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version