|
Problem |
Accessing data from DB2® v7.1 FP2a and later can result in
CLI0125E exceptions. |
|
Cause |
Default CURSORHOLD parameter set to FALSE. |
|
Solution |
In WebSphere® Application Server, the default value for
the CURSORHOLD parameter is set to FALSE, or 0. To resolve the CLI10125
exception, set the CURSORHOLD parameter to TRUE, or 1.
You can set this value as follows:
v3.5.3 and later releases of WebSphere Application Server 3.5
- Create a file called datasources.xml and place it in the
Install_Root\properties directory. The datasources.xml file must
contain the following directives:
<data-sources>
<data-source name="YourDataSourceName">
<attribute name="CURSORHOLD" value="1" >
</attribute>
</data-source>
</data-sources>
- Repeat the preceding highlighted directives for each data source that
has the problem.
v4.0 releases
- In the WebSphere administrative console, go to the data source that
has the problem:
- Click Add. At the bottom of the attribute list, in the Name field
type: connectionAttribute. In the Value field type:
cursorhold=1.
- Click Apply.
- Repeat for each DB2 v7.1 FP2a data source.
To update CURSORHOLD for the repository database
Edit admin.config and add this line:
com.ibm.ejs.sm.adminServer.dbCursorHold=true |
|
|
|
|
|
|