|
Problem IC70619
|
Status: Closed |
EXECUTING AN SQLJ SINGLETON SELECT STATEMENT WITH THE "SELECT INTO" CONSTRUCT MAY LEAD TO ERROR -4470 (RESULT SET IS CLOSED) |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When SQLJ runtime is used to execute a singleton select
statement which includes "SELECT INTO" construct, operation may
end abnormally throwing following exception:
com.ibm.db2.jcc.am.SqlException: [jcc][10120][10943][4.9.78001]
Invalid operation: result set is closed ERRORCODE=-4470,
SQLSTATE=null
at com.ibm.db2.jcc.am.ed.a(ed.java:660)
at com.ibm.db2.jcc.am.ed.a(ed.java:60)
at com.ibm.db2.jcc.am.ed.a(ed.java:103)
at com.ibm.db2.jcc.am.dn.yb(dn.java:3990)
at com.ibm.db2.jcc.am.dn.getFetchSize(dn.java:1126)
at
com.ibm.ws.rsadapter.jdbc.WSJccPreparedStatement.<init>(WSJccPre
paredStatement.java:176)
at
com.ibm.ws.rsadapter.jdbc.WSJccConnection.prepareSQLJStatement(W
SJccConnection.java:632)
at com.ibm.db2.jcc.sqlj.m.<init>(m.java:257)
at com.ibm.db2.jcc.sqlj.e.getStatement(e.java:137)
at
sqlj.runtime.ExecutionContext$StatementStack.setStatement(Execut
ionContext.java:1172)
at
sqlj.runtime.ExecutionContext.registerStatement(ExecutionContext
.java:695)
This problem is most likely to occur in IBM Websphere
Application Server (v7) environment. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* IBM Websphere Application Server (v7) *
****************************************************************
* PROBLEM DESCRIPTION: *
* When SQLJ runtime is used to execute a singleton select *
* statement which includes "SELECT INTO" construct, operation *
* may end abnormally throwing following exception: *
* com.ibm.db2.jcc.am.SqlException: *
* [jcc][10120][10943][4.9.78001] *
* Invalid operation: result set is closed ERRORCODE=-4470, *
* SQLSTATE=null *
* at com.ibm.db2.jcc.am.ed.a(ed.java:660) *
* at com.ibm.db2.jcc.am.ed.a(ed.java:60) *
* at com.ibm.db2.jcc.am.ed.a(ed.java:103) *
* at com.ibm.db2.jcc.am.dn.yb(dn.java:3990) *
* at com.ibm.db2.jcc.am.dn.getFetchSize(dn.java:1126) *
* at *
* com.ibm.ws.rsadapter.jdbc.WSJccPreparedStatement.<init>(WSJccP
* at *
* com.ibm.ws.rsadapter.jdbc.WSJccConnection.prepareSQLJStatement
* at com.ibm.db2.jcc.sqlj.m.<init>(m.java:257) *
* at com.ibm.db2.jcc.sqlj.e.getStatement(e.java:137) *
* at *
* sqlj.runtime.ExecutionContext$StatementStack.setStatement(Exec
* at *
* sqlj.runtime.ExecutionContext.registerStatement(ExecutionConte
* *
* *
* This problem is most likely to occur in IBM Websphere *
* Application Server (v7) environment. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB for LUW version 9.7.300 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 3
At a minimum, this fix should be applied on the client |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.08.2010
02.05.2011
02.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.300,
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
