DB2 - Problem description
Problem IC82438 | Status: Closed |
'UNEXPECTED MISSING SYSPLAN ENTRY' DB2DIAG.LOG RECORDS AFTER USE OF ANONYMOUS BLOCKS/COMPILED COMPOUND STATEMENTS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
After running an anonymous block, you might discover certain entries in db2diag.log, indicating a possible internal error about an "Unexpected missing SYSPLAN entry", that is not otherwise reported by DB2. For example: 2011-09-15-14.35.58.911000-240 I390816F594 LEVEL: Severe PID : 8920 TID : 1312 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : ISV1252 APPHDL : 0-11764 APPID: *LOCAL.DB2.110915201123 AUTHID : USER201 EDUID : 1312 EDUNAME: db2agent (ISV1252) FUNCTION: DB2 UDB, access plan manager, sqlra_mark_pkg_inoperative, probe:10 DATA #1 : String, 140 bytes Unexpected missing SYSPLAN entry. Package name = EDB .SQL151254210490000 Encountered during inoperation from EDB .JOBHIST of type T. These messages indirectly indicate the presence of a minor inconsistency in the DB2 system catalogs. However, the problem has no functional side-effects and your anonymous blocks should run correctly. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
This problem is fixed in DB2 Version 9.7 Fix Pack 6. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC87829 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.04.2012 05.06.2012 05.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |