Jul

Disaster Recovery (DR) Site for SAP ASE (Sybase) Database running with SAP Business Suite Applications

During the initial load and replication, the replication agent (RMA) reads the transaction log of the source database and generates the Log Transfer Language (LTL) output, which is a notation (using a language) that the replication server (SRS) uses to process identified and collected data throughout the replication channel from the source to the target database.

The primary replication server (SRS) receives the LTL from a replication agent and sends the replicated data to the companion replication server (Standby/DR Site) (when a split between primary replication server and replicate replication server is used). Otherwise, the sending does not take place because the data is operated by the single replication server instance). The companion replication server converts the received data from the LTL to the native format and language used by the target database. It sends the replicate data to the target database for processing, which closes the replication process (if it is committed in the target database).

For data consistency reasons (no loss of data) each replication server uses a database called the Replication Server System Database (RSSD) to store replication data and metadata. This information can be used by a replication agent to provide advanced replication features such as the transfer of database data logic (procedures).

There is a replication of DC & DR. For replication, the basic requirement is that both the databases need to be on the same DR side. In this particular case, the replication was stopped at the DR side & we did the migration of the entire DC Site’s database (taken from the client) along with the Transaction log to get the same in the same sync. Once it is done, the DC and DR get successfully synced under the replication configuration process.

In case you also face a similar issue, go through the following steps and overcome your concerns with utmost ease.

Sybase database load

Log in to windows server > USER > PRXXXX