|
Problem IC77187
|
Status: Closed |
FUNCTION: DB2 UDB, INDEX MANAGER, SQLICLEANUPEMPTYLEAF, PROBE:12 13 RETCODE : ZRC=0X87090054=-2029453228=SQLI_PRG_ERR "PROGRAM ER |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
a DB2 instance can encounter a programming error message during
an index update operation.
Possible stack :
pthread_kill
sqloDumpEDU
sqldDumpContext
sqlidelk
sqlidelk
sqldUpdateIndexes
sqlriupd
db2diag.log:
2011-06-15-14.12.56.240728+120 I103233A541 LEVEL: Severe
PID : 11075798 TID : 22950 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-6656 APPID: *LOCAL.SAMPLE.110615080414
AUTHID : db2inst1
EDUID : 22950 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, index manager, sqliCleanupEmptyLeaf,
probe:1213
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program
error"
DIA8575C An index manager programming error occurred.
2011-06-15-14.12.56.246447+120 I103775A749 LEVEL: Severe
PID : 11075798 TID : 22950 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-6656 APPID: *LOCAL.SAMPLE.110615080414
AUTHID : db2inst1
EDUID : 22950 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary
logging fu, probe:0
DATA #1 : String, 173 bytes
Running the following command before and after restart database
may provide useful problem determination information.
Replace DBNAME with the real DB name if not provided.
DATA #2 : String, 91 bytes
db2dart S83CFLS /di /tsi 2 /oi 9 /ps 63172p /np 1 /v y /scr n
/rptn iTsi2oi9pg63172p+0.rpt
...
2011-06-15-14.16.37.363077+120 E403729A974 LEVEL:
Critical
PID : 11075798 TID : 22950 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB :
S83CFLS
APPHDL : 0-6656 APPID: *LOCAL.SAMPLE.110615080414
AUTHID : db2inst1
EDUID : 22950 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::MarkDBBad, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred:
"DBMarkedBad". The instance may have been shutdown as
a result.
"Automatic" FODC (First Occurrence Data Capture) has
been invoked and
diagnostic information has been recorded in directory
"/home/db2inst1/sqllib/db2dump/FODC_DBMarkedBad_2011-06-15-14.1
6.37.316103/". Please look in this directory for
detailed evidence
about what happened and contact IBM support if
necessary to diagnose
the problem.
The database will get marked as bad, and will require Crash
recovery. However the databsae should complete crash recovery
without any problems. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* FUNCTION: DB2 UDB, INDEX MANAGER, SQLICLEANUPEMPTYLEAF, *
* PROBE:12 *
* 13 RETCODE : ZRC=0X87090054=-2029453228=SQLI_PRG_ERR *
* "PROGRAM ERRROR" *
****************************************************************
* RECOMMENDATION: *
* Upgrade to to DB2 v9.5 Fixpack 9 *
**************************************************************** |
| Local Fix: |
To avoid hitting problem, the customer should COMMIT any CREATE
INDEX statements immediately after the CREATE INDEX statement
has completed, instead of including the CREATE INDEX as a part
of a larger transaction. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 v9.5 Fixpack 9 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC77761
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.06.2011
08.03.2012
08.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
