Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87829 Status: Closed

'UNEXPECTED MISSING SYSPLAN ENTRY' DB2DIAG.LOG RECORDS AFTER USE
OF ANONYMOUS BLOCKS/COMPILED COMPOUND STATEMENTS

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:


Solution


This problem is fixed in DB2 Version 10.1 Fix Pack 1.


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.11.2012
06.11.2012
06.11.2012


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)