Meaningless Drivel is fun!*
The moose likes EJB and other Java EE Technologies and the fly likes WSAD 4.03,SQL Server 2000  -- Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "WSAD 4.03,SQL Server 2000  -- "FOR UPDATE cannot be specified on a READ ONLY cursor"" Watch "WSAD 4.03,SQL Server 2000  -- "FOR UPDATE cannot be specified on a READ ONLY cursor"" New topic
Author

WSAD 4.03,SQL Server 2000 -- "FOR UPDATE cannot be specified on a READ ONLY cursor"

CL Fisher
Greenhorn

Joined: Oct 30, 2002
Posts: 1
Greetings, all
In my current J2EE project, I have a number of CMP Entity EJBs that are working well against a local DB2 database. However, I need to work against a remote MS SQL Server 2000 db.
I can connect to said db, and can do normal JDBC updates against it using the datasource I have set up for the EJBs.
I can create an EJB -- the row shows up in the remote database. However... when I do a setNote (note being the only non-key field in the EJB), I get the following exception:

RemoteException occurred in server thread; nested exception is:
com.ibm.websphere.cpi.CPIException: java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]FOR UPDATE cannot be
specified on a READ ONLY cursor.; nested exception is:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]FOR UPDATE cannot be specified on a READ ONLY cursor.

Has anyone encountered this, or have ideas about what may cause it?
Many thanks in advance,
CL
HanMing Low
Ranch Hand

Joined: Oct 18, 2001
Posts: 196
Hi,
I think this has been answered a few days back.
The problem is either WebSphere does not support EJB 2.0 or the SQL Server JDBC Driver by MS is not supported by WS.
Hope this helps.
Cheers.

Han Ming
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
My guess is that HanMing's second guess is right -- looking at the WAS 4.02 product set shows that the Microsoft driver wasn't supported in WAS AEs 4.02 but now IS in WAS 4.04.
SO.... you MIGHT be ok if you install the WAS 4.04 fixpack on top of the WAS AEs installation in WSAD. Such things have worked before...
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WSAD 4.03,SQL Server 2000 -- "FOR UPDATE cannot be specified on a READ ONLY cursor"
 
Similar Threads
Getting SQL Exception although stored procedure is correct!!!
Problem with CMP using MS SQL Server 2000
forum regarding insert data
Why my sqlserver2000 CMP could not work ?
Could not Create Connection in MS SQL Server 2000