suche 36x36
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 IT22367 Status: Closed

AN SQL0901N "EXPECTING CACHED ZVAL FOR MARKED PID" IS POSSIBLE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
db2diag.log will have this message: 
 
sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 36 
sqlerrmc: Expecting cached zval for marked pid 
 
Stack in the FODC directory will have this: 
 
sqlng_process_parse_tree_node 
sqlng_process_BF_node 
sqlng_walk_EXPR_chain 
sqlng_build_thread 
sqlngPrecomputeInvariantPreds 
... 
 
where sqlngPrecomputeInvariantPreds is the key to identifying 
this issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* issue found in : db2_v111m1fp2                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product version db2_v111m3fp3                     * 
****************************************************************
Local Fix:
db2set DB2_TCG_DEFAULT_OPTIONS="set precompute_expr off" 
<instance restart>
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.09.2017
15.03.2018
15.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)