SAP Knowledge Base Article - Preview

2131436 - Suspend and resume DSI can cause skipped transactions - SRS Parallel DSI

Symptom

  • Parallel DSI (dsi_num_threads > 1, parallel_dsi='on')
  • Internal commit control (dsi_commit_control='on')

When using parallel DSI and dsi_commit_control 'on', it is possible for a transaction(s) to not be applied to the replicate after a suspend/resume DSI has occurred.  This results in missing data at the replicate and the primary and replicate databases to be out of sync.


Read more...

Environment

  • SAP Replication Server (SRS)
  • SAP Replication Server Real Time Loading
  • SAP Replication Server Heterogeneous Edition
  • SAP Replication Server Option for IBM DB2
  • SAP Replication Server Option for Oracle
  • SAP Replication Server Option for Microsoft SQL Server

Product

SAP Replication Server all versions ; SAP Replication Server, heterogeneous edition all versions ; SAP Replication Server, option for IBM DB2 all versions ; SAP Replication Server, option for Microsoft SQL Server all versions ; SAP Replication Server, option for Oracle all versions ; SAP Replication Server, real-time loading edition all versions

Keywords

missing, txn,  tran, 'row count validation', sync, dsi_commit_control , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , BC-SYB-REP-HET , Replication Server Heterogeneous Edition (RSHE) , BC-SYB-REP-RTL , Rep Server Real-Time Loading Edition (RTLE) , BC-SYB-REP-ME , Replication Server Messaging Edition (RSME) , BC-SYB-REP-RSO , Rep Server Options (RSO) , Bug Filed

About this page

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

Search for additional results

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