Skip to Content

SAP Replication Server - can we set abort log on full for primary database?

Sep 16, 2017 at 01:41 PM


avatar image
Former Member


Is there any issue if we setup 'abort tran on log full' for primary database? Does sybase try to kill repagent process in case replication marker is blocking the transaction? Kindly advise.


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Mark A Parsons Sep 16, 2017 at 02:37 PM

Setting abort tran on log full should not be an issue.

Keep in mind the PDB transaction log will only be truncated up to the (replication) secondary trunc point.

At no time will the dataserver attempt to kill the repagent, nor will the dataserver attempt to remove the (replication) secondary trunc point.

If the (replication) secondary trunc point is causing the PDB transaction log to fill up then the DBA will need to perform some action to remedy the situation, eg:

  • extend the PDB transaction log
  • address/fix the issue causing the repagent to fall behind
  • stop the repagent and drop the (replication) secondary trunc point [NOTE: This will break replication and require the DBA to perform resync operations if/when it's decided to resume replication.]
10 |10000 characters needed characters left characters exceeded