|
Problem IT09300
|
Status: Closed |
ENABLE EXTENDED INDICATOR AND REOPT ALWAYS MAY CAUSE INSTANCE CRASH |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When extended indicator and REOPT ALWAYS are enabled, db2
instance may trap in stacks as following:
stack 1:
sqlraExtendedIndicatorDescriptor::selectiveCopy
sqlra_load_var
sqlra_get_var
sqlrr_process_execute_request
sqlrr_execute
sqljs_ddm_excsqlstt
sqljsParseRdbAccessed
sqljsParse
sqljsSqlam
sqljsDriveRequests
sqljsDrdaAsInnerDriver
sqljsDrdaAsDriver
sqeAgent::RunEDU
stack 2:
__PRETTY_FUNCTION__.6093
sqlraExtendedIndicatorDescriptor::selectiveCopy
sqlra_get_var
sqlrr_process_execute_request
sqlrr_execute
sqljs_ddm_excsqlstt
sqljsParseRdbAccessed
sqljsParse
sqljsSqlam
sqljsDriveRequests
sqljsDrdaAsInnerDriver
sqljsDrdaAsDriver
sqeAgent::RunEDU
In a java application connecting to DB2 with JCC driver,
enableExtendedIndicators is turned on by default, if
currentPckageSet is set to NULLIDRA (NULLIDRA PackageSet is
bound with the REOPT ALWAYS bind option by default) at the same
time, this problem may happen.
This APAR addresses the issue which APAR IT03348 doesn't fix
completely. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.5 FIXPACK 7. *
**************************************************************** |
| Local Fix: |
1) Disable extended Indicator, an example in JCC application:
String url = "jdbc:default:connection";
Properties prop = new Properties();
prop.put("enableExtendedIndicators", "2");
try {
con = DriverManager.getConnection(url, prop);
...
or
2) Disable REOPT ALWAYS, use either NONE or ONCE instead; don't
use PackageSet NULLIDRA. |
| Solution |
The problem is firstly fixed on V10.5 FIXPACK 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.06.2015
20.01.2016
20.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
