DB2 - Problembeschreibung
Problem IC82667 | Status: Geschlossen |
HADR STANDBY FAILED TO START WITH ERROR SQLD_PRGERR | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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: * * Only HADR environments are affected * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7.0.6. * **************************************************************** | |
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 | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
The problem is first fixed in DB2 version 9.7.0.6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC98043 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.04.2012 04.06.2012 04.12.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.0.6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |