Feedback
Did this article resolve your question/issue?

   

Article

Serialization failure while working with Connect for ODBC Sybase driver

Information

 
TitleSerialization failure while working with Connect for ODBC Sybase driver
URL NameSerialization-failure-while-working-with-SYBASE-DB
Article Number000185003
EnvironmentProduct: Connect for ODBC Sybase
Version: 7.15
OS: Linux
Database: Sybase 15
Application: All supported applications
Question/Problem Description
After upgrading to Connect for ODBC Sybase Version 7.1, when calling a Stored procedure that encounteres a deadlock situation.
The application intercepts this and sends a SQLTransact(). The SQLTransact fails (SQL_ERROR) and the mentioned error is thrown.
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC Sybase Wire Protocol driver]Serialization failure.
Defect Number
Enhancement Number
Cause
The “Serialization failure” error is returned by our driver as the server is aborting the statement.

From msdn Spec for “SQLEndTran()”

40001 Serialization failure The transaction was rolled back due to a resource deadlock with another transaction.
Resolution
Contact SupportLink and refer to this KB article.
Workaround
Notes
Last Modified Date11/20/2020 7:25 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.