SAP Knowledge Base Article - Preview

1959030 - How To Salvage Data When There are Corrupt Pages in the Database

Symptom

While using SQL Anywhere, database corruption is possible due to both software and hardware issues. When a database corruption is detected by SQL Anywhere, the database will provide an assertion message and take remedial actions (See: KBA 1958942).

A frequent and potentially correctable type of database assertion related to database corruption is related to table data on specific tables. When this happens, an assertion message with the text:

   *** ERROR *** Assertion failed: 201501 (x.x.x.xxxx)
Page for requested record not a table page or record not present on page.

or

   *** ERROR *** Assertion failed: 101412 (x.x.x.xxxx)

Page number on page does not match page requested

will be shown in the database console log.

If there are no available valid backups of the database available from your backup and recovery strategy, it may be desirable to attempt to extract all information that is still available in the accessible areas of the database.


Read more...

Environment

SAP SQL Anywhere (all platforms, all versions)

Product

SAP SQL Anywhere 16.0 ; SAP SQL Anywhere, cloud edition 1.0 ; SAP Sybase SQL Anywhere 12.0 ; Sybase SQL Anywhere 10.0 ; Sybase SQL Anywhere 11.0

Keywords

Sybase, backup, crash, corruption, SQL, SQLAny, SQLA, assert, assertion, fail, failed, valid, validation, db, , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , How To

About this page

This 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.