DB2 - Problembeschreibung
Problem IC89543 | Status: Geschlossen |
SQLB_EMP_MAP_INFO_NOT_FOUND FROM SQLBPFTRIGGERPREFETCH IN DB2DIAG.LOG | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
After running REORG with RECLAIM EXTENTS on indexes located in old tablespaces (created in versions of DB2 earlier than Version 9.7) an error like the following might appear in the db2diag.log triggered by the collection of RUNSTATS. FUNCTION: DB2 UDB, buffer pool services, sqlbpfTriggerPrefetch, probe:3688 MESSAGE : ZRC=0x8402001B=-2080243685=SQLB_EMP_MAP_INFO_NOT_FOUND "EMP MAP INFO NOT FOUND" [...] FUNCTION: DB2 UDB, buffer pool services, sqlbpfTriggerPrefetch, probe:3688 DATA #1 : String, 136 bytes Obj={pool:7;obj:75;type:1} State=x27 Parent={6;77}, EM=956, PP0=958 The Extent should have been allocated: start page 310 number exts 5 [...] FUNCTION: DB2 UDB, buffer pool services, sqlbpfTriggerPrefetch, probe:0 DATA #1 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 96 bytes Obj: {pool:7;obj:75;type:1} Parent={6;77} [...] FUNCTION: DB2 UDB, buffer pool services, sqlbpfTriggerPrefetch, probe:3688 MESSAGE : ZRC=0x8402001B=-2080243685=SQLB_EMP_MAP_INFO_NOT_FOUND "EMP MAP INFO NOT FOUND" [...] DB2 UDB, data management, sqld_seqdet_initiate_prefetch DATA #3 : String, 14 bytes prefetchFlags: DATA #4 : Hex integer, 4 bytes 0x00000000 [...] CALLSTACK: sqlbpfTriggerPrefetch sqld_seqdet_initiate_prefetch sqldSeqDetPage sqliPerformPrefetching sqlischs sqlistat sqldIndexStats sqlrLocalRunstats sqlrrsta [...] FUNCTION: DB2 UDB, buffer pool services, sqlbpfTriggerPrefetch, probe:3934 MESSAGE : ZRC=0x8402001B=-2080243685=SQLB_EMP_MAP_INFO_NOT_FOUND "EMP MAP INFO NOT FOUND" DATA #1 : String, 23 bytes Prefetch Error Ignored. The error does not cause RUNSTATS to fail. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 Fix Pack 3 * **************************************************************** | |
Local-Fix: | |
1) Recreate affected indexes, which can be identified by querying syscat.indexes table: $ db2 "select INDSCHEMA, INDNAME, TBSPACEID, INDEX_OBJECTID from syscat.indexes where TBSPACEID=pool AND INDEX_OBJECTID=obj" substituting pool and obj numbers with the numbers specified in the db2diag.log 2) do not run REORG with RECLAIM EXTENTS for indexes located in old tablespaces (pre DB2 Version 9.7). | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
The problem is first fixed in DB2 version 10.1 Fix Pack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.01.2013 01.10.2013 23.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |