Error 226: SET CHAINED command not allowed within multi-statement transaction
Effect:
Throws the exception of com.sybase.jdbc2.jdbc.SybSQLException with error code 226 and an SQL state of ZZZZZ.
Cause:
This exception is usually caused by a defect in older versions of jConnect.
Error 7112: Stored procedure 'x' may be run only in chained transaction mode
Effect:
Throws the exception of com.sybase.jdbc2.jdbc.SybSQLException with error code 7712 and an SQL state of ZZZZZ.
Cause:
The stored procedure was created in chained mode, or later altered to run in chained mode, but the driver is currently running in unchained mode. The probable cause is that the Use Manual Transactions? parameter is set to . Another possibility is that the transaction type has been overridden to in a policy.
Solution:
Do one of the following:
-
Use stored procedure sp_procxmode to change the stored procedure's mode to or (preferred).
-
Change the driver's Use Manual Transactions? parameter to , or change the policy transaction type to .
Error 7113: Stored procedure 'x' may be run only in unchained transaction mode
Effect:
Throws the exception com.sybase.jdbc2.jdbc.SybSQLException with error code 7713 and an SQL state of ZZZZZ.
Cause:
The stored procedure was created in unchained mode, or later altered to run in unchained mode, but the driver is currently running in chained mode. The probable cause is that the Use Manual Transactions? parameter is set to . Another possibility is that the transaction type has been overridden to in policy.
Solution:
Do one of the following:
-
Use stored procedure sp_procxmode to change the stored procedure's mode to or (preferred).
-
Change the driver's Use Manual Transactions? parameter to , or change the policy transaction type to .
If you set use-manual-transactions to , all transactions consist of a maximum of one statement.