CLI0627E The result set is not scrollable.

[Deepa Raj]

hi All,

i m using WSAD5.1.2 , JDBC 2.0 , DB2 7.2.3 .

i m getting the following exception.Plz help me to rectify this.
[11/14/05 18:30:01:515 IST] 6900690 SystemErr R java.sql.SQLException: [IBM][JDBC Driver] CLI0627E The result set is not scrollable.
[11/14/05 18:30:01:531 IST] 6900690 SystemErr R at java.lang.Throwable.<init>(Throwable.java)
[11/14/05 18:30:01:531 IST] 6900690 SystemErr R at java.lang.Throwable.<init>(Throwable.java)
[11/14/05 18:30:01:531 IST] 6900690 SystemErr R at java.sql.SQLException.<init>(SQLException.java:90)
[11/14/05 18:30:01:531 IST] 6900690 SystemErr R at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throwNotScrollable(SQLExceptionGenerator.java:761)
[11/14/05 18:30:01:531 IST] 6900690 SystemErr R at COM.ibm.db2.jdbc.app.DB2ResultSet.getRow(DB2ResultSet.java:3188)

thanks.

[Ram Mohan]

Did you make it Scroll Intensive.

smt = con.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_UPDATABLE);


Ram Mohan

[Deepa Raj]

Hi ,

Actually we are using , Callable Statement.......One more thing the same code is working in onsite.but in offshore its not working......

[Maximilian Xavier Stocker]

Originally posted by Deepa Raj:
Hi ,

Actually we are using , Callable Statement.......One more thing the same code is working in onsite.but in offshore its not working......

Then this is a deployment issue. You don't have the same version of code or stored proc on the offshore version as you do onsite.

[Deepa Raj]

Originally posted by Maximilian Stocker:


Then this is a deployment issue. You don't have the same version of code or stored proc on the offshore version as you do onsite.

Hi ,

Actually we r hitting onsite Stored procedure only....code and SP are same ....but something JDBC driver problem....we r using DB27.1 but Onsite is using DB27.2 ... is it any problem?

Thanks.

[Paul Clapham]

You were looking for something in your configuration that was different between the two sites. Now you have found something.

If it were me I would change the non-working site to be configured the same as the working site. Even though I have no idea whether that difference is the problem or not.