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 IT03682 Status: Closed

DB2 MIGHT TRAP IN SQLPLRQ() WITH REOPT ENABLED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The DB2 Server might encounter a trap in sqlplrq() function if 
REOPT is enabled for the statement being executed. 
 
A typcial stack trace you might see in the trap file: 
 
<sqlplrq> <sqlplrq.C:2858> 
<sqlrr_get_lock> <sqlrr_lock.C:333> 
<sqlra_get_var> <sqlra_var.C:2201> 
<sqlrr_process_open_request> <sqlrr_req_sql.C:5307> 
<sqlrr_open> <sqlrr_req_sql.C:1984> 
<sqljs_ddm_opnqry> <sqljsqry.C:1030> 
<sqljsParse> <sqljspar.C:887> 
<sqljsSqlam> <sqljsqam.C:2190> 
<sqljsDriveRequests> <sqljsqam.C:3065> 
<sqljsDrdaAsInnerDriver> <sqljsqam.C:1277> 
<sqljsDrdaAsDriver> <sqljsqam.C:1052> 
<sqeAgent::RunEDU> <sqle_agent.C:4052> 
<sqlzRunEDU> <sqlz_edu_obj.C:35> 
<sqloEDUEntry> <sqloedu.C:3454>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.08.2014
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList