SAP Knowledge Base Article - Preview

2141176 - "Recovery Fault Isolation (RFI)" to fix corruption errors on database recovery, load transaction - SAP ASE

Symptom

  • Corruption errors are reported against one of more ASE tables and/or indexes in the following scenarios:
  1. user database recovery during ASE boot/start-up
  2. SID database recovery on systems running SAP applications
  3. load transaction
  4. load database
  • The errors are related to table or index page-level corruption.
    Some examples of the errors are: Error 605, Error 692, Error 691, Error 631, Error 625, Error 644, Error 2503, Error 2628, Error 12546, Error 3474, Error 12313, Error 632.
  • The errors prevent the ASE database from being recovered successfully and/or prevent  transaction log records from being applied during recovery.
    Due to this, the entire database is rendered offline and marked "suspect" even though only one or a few corrupt objects might exist.
  • The safest and advisable way to correct this situation is by restoring the database from a latest, clean backup. On SAP systems, an import/export method using file-system backups can also be used.
  • Many a time, restoring an older, clean copy of the database or a database rebuild, is not feasible - and they may lead to a significant loss of data and transactional activity.
  • If there is no clean, recent database backup available, or an SAP import/export is not possible: use "Recovery Fault Isolation" (RFI) to bypass the offending ASE corruption errors and corresponding corrupt pages - and bring the database online.
  • With RFI, users can still access the database in it's current transactional and operational state.
  • You can plan to fix the affected object(s) once the database is online; by rebuilding the affected object(s) -- via t-code SE14 on SAP systems or via select into / bcp
  • The RFI procedure does not apply to system databases or system tables belonging to user & system databases.
  • Almost all corruption-related ASE errors are handled by RFI including but not limited to:  605, 692, 695, 644, 3474, 1125, 1141, 1134, 1152, 1131, 1142, 1143, 1135, 6902, 3301, 3311, 3312, 12300, 12308, 12312, 12313

Read more...

Environment

  • SAP Adaptive Server Enterprise 15.7
  • SAP Adaptive Server Enterprise 16.0

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

corruption, syslogs, backups, suspect, LOAD TRANSACTION, recovery, 632, 12313, 3474, 692, RFI, CR 681822, 711785, 605, 692, 691, 631, 625, 644, 2503, 2628, 12546, 3474, 12313, 632 , KBA , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.