SAP Knowledge Base Article - Preview

2568836 - Some data are not replicated when a partial rollback is executed on primary database - SRS


  • In a SAP Replication system, when a partial rollback is executed on the Primary Database, it can be unexpectedly discarded by replication. This will result in a data mismatch between the Primary Database and the Replicate Database.
  • The problem is hard to reproduce as it occurs only when :
    • multiple connections to the Primary Database are working simultaneously
    • connections are using user transactions
    • user transactions are including partial rollback
  • Below is a sample example of code which is including a partial rollback:

begin tran

 exec Proc_P1

 save tran TR1
   update table
 rollback tran TR1

 exec Proc_P2
commit tran

  • This problem can generate a lot of different messages associated to fact that the Primary and the Replicate database are no more synchronized:
    • Message: 2601, State 2, Severity 16 -- 'Attempt to insert duplicate key row in object '<table_name>' with unique index '<table_index>' 
    • error about row count validation :
      • 5186 / 5186
                 Row count mismatch for the command executed on ‘<dataserver.database>’.
                 The command impacted <x> rows but it should impact <y> rows.



  • SAP Replication Server (SRS) 15.7.1
  • SAP Replication Server (SRS) 16.0
  • SAP Adaptive Server Enterprise (ASE) 16.0


SAP Adaptive Server Enterprise 16.0 ; SAP Replication Server 15.7 ; SAP Replication Server 16.0


SRS, Replication server, rep server, data mismatch, CR808280, CR#808280, 808280, duplicate key, missing row, row count, 2601, 5185, 5186 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-REP , Sybase Replication Server (standalone) , 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.