This article provides troubleshooting tips for accessing Sybase data sources.
To fix the autocommit(true) mode problem, let the application change the connection to chained mode using the Connection.setAutoCommit(false) mode, or use a set chained on language command.
To resolve the stored procedure problem, use the sp_procxmode procedure_name "anymode" command.
This error occurs when XA-style transactions are attempted on a server that does not have Distributed Transaction Management (DTM) installed.
This error is caused by improper use of reserved words. Reserved words cannot be used as column names.
To correct this problem: Rename the variable to remove the reserved word. You can find a list of reserved words in the Quick Reference Guide for Sybase Adaptive Server Enterprise 15.5. This manual is available online at: http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc70202.1550/html/quickref/CACIGGEB.htm.
Verify that your database name is correctly entered on the data source properties.
Most databases (DB2®, Oracle, Informix® , MS SQL Server and Apache Derby) throw an exception when the database specified does not exist. But Sybase does not throw an exception when an incorrect database name is specified. Sybase generates an SQL warning and then connects to the default database. If you misspell the requested database name, Sybase connects you to the master or the default database where the table you requested is not found.
If none of these steps fixes your problem, check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes). If you do not find your problem listed there, contact IBM Support.