SAP Knowledge Base Article - Preview

3725492 - Transaction Log Filling on SAP ASE DR System Without Backup Scheduling - ASE

Symptom

In an SAP system running on SAP Adaptive Server Enterprise (ASE), the transaction log device on the Disaster Recovery (DR) ASE system frequently becomes full.

This may lead to:

  • Replication interruption between Primary ASE and DR ASE

  • Errors indicating transaction log full

  • Database operations stopping due to lack of available log space

 


Read more...

Environment

  • SAP systems running on SAP Adaptive Server Enterprise (ASE)

  • SAP Java-based systems

  • Landscapes with Primary, Standby, and DR ASE systems

  • Backup solutions configured only on Primary and Standby, but not on DR

  • Replication configured from Primary ASE → DR ASE

Example landscape:

  • Site 1: Primary ASE

  • Site 2: Standby ASE

  • Site 3: DR ASE

Product

SAP NetWeaver 7.5

Keywords

transaction log full, dump transaction, DR ASE, replication interruption, ASE backup scheduling, SAP Java ASE backups , KBA , BC-DB-SYB , Business Suite 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.