SAP Knowledge Base Article - Preview

2315399 - Transaction log suicide via "dump transaction with no_log" not allowed - SAP ASE for Business Suite

Symptom

  • Running a SAP ERP application on ASE database.
  • The system runs into irreparable and irreversible ASE error conditions. Not limited to these, but example errors include:
    • ASE transaction log is completely full (Error 1105/3475)
    • ASE transaction log is corrupt (Error 695/834)
    • The database is subsequently inaccessible and unrecoverable
  • You are considering truncating the ASE transaction log withh the database in bypass recovery mode (aka suicide log procedure), in order to clear the above conditions.

  • When executing the 'dump tran' command
  • Error 4246 is returned
     
    dump tran db1 with no_log

    go

    Msg 4246, Level 16, State 1:
    Server 'ASE', Line 1:
    Warning: You cannot run DUMP TRANSACTION WITH NO_LOG for a database that is in bypass recovery mode because this can cause data inconsistency.
    Use the command 'dump tran db1 with no_log, force_key=12345' to bypass this restriction.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 for Business Suite
  • SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite
  • SAP Adaptive Server Enterprise (ASE) (all versons)

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

dump, transaction, corrupt, suicide, no_log, rebuild_log, CR784167, CR#784167, 784167 , KBA , nolog , saucide log , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.