- During start-up or during operation of the SAP SQL Anywhere database, there is an erroneous operating condition encountered and an error message is printed to the database console log:
*** ERROR *** Assertion failed: ###### (x.x.x.xxxx)
Error message follows with information about the cause of the assertion.
The assertion number is a six-digit number, and the numbers following the assertion number in brackets will indicate the version and build of the SQL Anywhere database server that asserted. Details about the assertion are provided in a text line following the error.
- A client connection that is already connected to the database or attempts to connect to the database may also see the error:
Internal database error "Assertion failed: 123456 (xx.x.x.xxxx)" -- transaction rolled back
SQLCODE=-301, ODBC 3 State="40W01"
No other work may be performed on the database server and all futher SQL commands will result in the reported client error.
- At the time of the assertion message, the SQL Anywhere database server will also produce a diagnostic .DMP file and .CRASH_LOG file in the SADIAGDIR environment variable's file path with the file name prefix:
Where 'SA1X' is the major version of SQL Anywhere, 'YYYYMMDD' is the date on which the assertion occurred, the 'HHmmss' is the time of day the assertion occurred and 'pid' is the Process ID of the crashing process.
Running the Support Utility (dbsupport) with 'dbsupport -lc' may list this same entry as an outstanding crash entry to be submitted to SAP Support.
SAP Sybase SQL Anywhere (all versions, all platforms)
SQL, Anywhere, SQLAny, SQLA, assert, fail, failed, error, errors, db, database, msg, nessage, fails , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.