Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SET CHAINED OFF Error in Sybase ASE15

134 views
Skip to first unread message

Swastik

unread,
Jan 21, 2010, 11:15:57 AM1/21/10
to
Hello,

I am getting SET Chanined off error while trying run an update query
from Java using jconnect6/jdbc3 to Sybase ASE 15 Database. The
surprising this is that; it gives this type of error for Stored procs;
but it's giving the error for a Update query getting picked up on run
time from a SQL file kept at a unix location by the java code. That's
the reson the stored Proc name it's throwing is a machine number and
not any actual stored Proc Name!!

AD300|Unable to update ExtEntityID table.|Class:
ExternalEntityUpdtQuery; Error Desc:
com.sybase.jdbc3.jdbc.SybSQLException: Stored procedure
'*00093100000001_1a30fd' may be run only in unchained transaction
mode. The 'SET CHAINED OFF' command will cause the current session to
use unchained transaction mode.

java.lang.Exception: Class: ExternalLegalEntityUpdtQuery; Error Desc:
com.sybase.jdbc3.jdbc.SybSQLException: Stored procedure
'*00093100000001_1a30fd' may be run only in unchained transaction
mode. The 'SET CHAINED OFF' command will cause the current session to
use unchained transaction mode.


Any input will be appreciated.

Thanks,
Swastik

Swastik

unread,
Jan 21, 2010, 6:25:03 PM1/21/10
to
We resolved the issue!! :-)
We were passing the following line while connecting to the Database
from java:

driverprops=IS_CLOSED_TEST=INTERNAL,JCONNECT_VERSION=6,DYNAMIC_PREPARE=true

And that was creating this issue.

Paul Vero [Sybase]

unread,
Jan 25, 2010, 5:45:41 PM1/25/10
to
Hi,

What version jConnect are you using?

Sounds like you created the procedure in a specific mode - unchained mode.

Then with dynamic prepare - this option will create procedures for queries
you send
through and probably it was created initially in unchained mode then when
the execution happens,
when parameters are sent, maybe application setAutoCommit to false, setting
the session to chained mode
and then you get that error.

Let me know the version - if you want to use those options - i can check and
see if there's
some change in the driver to alleviate that error.

Thank you

-Paul

"Swastik" <swas...@gmail.com> wrote in message
news:dd0accd6-09aa-4567...@a6g2000yqm.googlegroups.com...

0 new messages