Detecting Loss for Database

Usually occurs after a rebuild queues command is executed. This command is typically issued after a stable device failure.

Symptom

After you have issued the rebuild queues command and the data loss detection process has completed, see the Loss Status column in the output from admin health and admin who, sqm to check for data loss in the queues, or data loss detection messages in the SAP Replication Server error log. Perform data loss detection only when there are primary transactions to be replicated. The SAP® Control Center for Replication Perspective Heat Chart view displays the monitoring statistics of possible data loss between the primary and replicate databases .

Note: Sometimes these messages do not appear at the end of the error log file, so you must search back through the log for them. If you restart the SAP Replication Server, these messages appear again.

I. 2006/06/13 15:48:32. Rebuild Queues: Starting
I. 2006/06/13 15:48:33. Disconnecting Replication Agent
for westss.westrs_rssd. Replication Agent will shutdown
I. 2006/06/13 15:48:33. Disconnecting Replication Agent
for westss.westrs_rssd to Rebuild
I. 2006/06/13 15:48:33. Resetting Replication Agent
starting log position for westss.westrs_rssd
I. 2006/06/13 15:48:33. Resetting Replication Agent
starting log position for westss.eastlp
I. 2006/06/13 15:48:33. Shutting down distributor for
101.
I. 2006/06/13 15:48:33. A request to shutdown/suspend
the distributor for 101 has been received.
I. 2006/06/13 15:48:33. The distributor for
'westss.westrs_rssd' is shutting down
I. 2006/06/13 15:48:33. Shutting down distributor for
102.
I. 2006/06/13 15:48:33. A request to shutdown/suspend
the distributor for 102 has been received.
I. 2006/06/13 15:48:34. The distributor for
'westss.eastlp' is shutting down
I. 2006/06/13 15:48:34. Shutting down the DSI thread for
'westss.westrs_rssd'.
I. 2006/06/13 15:48:34. The DSI thread for database
'westss.westrs_rssd' is shutdown.
I. 2006/06/13 15:48:34. DSI: enabled loss detection for
'westss.westrs_rssd'.
I. 2006/06/13 15:48:34. Shutting down the DSI thread for
'westss.eastlp'.
I. 2006/06/13 15:48:34. The DSI thread for database
'westss.eastlp' is shutdown.

I. 2006/06/13 15:48:34. DSI: enabled loss detection for
'westss.eastlp'.
I. 2006/06/13 15:48:34. Shutting down the DSI thread for
'westss.westlp'.
I. 2006/06/13 15:48:35. The DSI thread for database
'westss.westlp' is shutdown.
I. 2006/06/13 15:48:35. DSI: enabled loss detection for
'westss.westlp'.
I. 2006/06/13 15:48:35. Rebuild queues: deleting queue
103:0
I. 2006/06/13 15:48:35. SQM stopping: 103:0
westss.westlp
I. 2006/06/13 15:48:35. Rebuild queues: done rebuilding
queue 103:0. Restarting.
I. 2006/06/13 15:48:35. Rebuild queues: deleting queue
102:1
I. 2006/06/13 15:48:35. SQM stopping: 102:1
westss.eastlp
I. 2006/06/13 15:48:35. SQM starting: 103:0
westss.westlp
I. 2006/06/13 15:48:35. Rebuild queues: done rebuilding
queue 102:1. Restarting.
I. 2006/06/13 15:48:35. Rebuild queues: deleting queue
102:0
I. 2006/06/13 15:48:36. SQM stopping: 102:0
westss.eastlp
I. 2006/06/13 15:48:36. SQM starting: 102:1
westss.eastlp
I. 2006/06/13 15:48:36. Rebuild queues: done rebuilding
queue 102:0. Restarting.
I. 2006/06/13 15:48:36. Rebuild queues: deleting queue
101:1
I. 2006/06/13 15:48:36. SQM stopping: 101:1
westss.westrs_rssd
I. 2006/06/13 15:48:36. SQM starting: 102:0
westss.eastlp
I. 2006/06/13 15:48:36. Rebuild queues: done rebuilding
queue 101:1. Restarting.
I. 2006/06/13 15:48:36. Rebuild queues: deleting queue
101:0
I. 2006/06/13 15:48:36. SQM stopping: 101:0
westss.westrs_rssd
I. 2006/06/13 15:48:36. SQM starting: 101:1
westss.westrs_rssd
I. 2006/06/13 15:48:37. Rebuild queues: done rebuilding
queue 101:0. Restarting.
I. 2006/06/13 15:48:37. SQM starting: 101:0
westss.westrs_rssd
I. 2006/06/13 15:48:37. Starting DIST for 101:1.
I. 2006/06/13 15:48:37. Starting DIST for 102:1.
I. 2006/06/13 15:48:37. DIST for 'westss.westrs_rssd'
is Starting
I. 2006/06/13 15:48:37. DIST for 'westss.pdb' is
Starting
I. 2006/06/13 15:48:37. Starting the DSI thread for
'westss.westrs_rssd'.
I. 2006/06/13 15:48:38. Starting the DSI thread for
'westss.westlp'.
I. 2006/06/13 15:48:38. The DSI thread for database
'westss.westrs_rssd' is started.
I. 2006/06/13 15:48:39. Starting the DSI thread for
'westss.eastlp'.
I. 2006/06/13 15:48:40. The DSI thread for database
'westss.eastlp' is started.
I. 2006/06/13 15:48:41. The DSI thread for database
'westss.eastlp' is started.
I. 2006/06/13 15:48:41. Rebuild Queues: Complete
I. 2006/06/13 15:48:44. DSI: detecting loss for database
'westss.eastlp' from origin 'westss.westlp' date = 
'Jun 13 2006  2:36:49:783PM', qid=0000000000001d
240000054b00090000054b0007000097df00f0d41700000000000
0001.

Explanation

SAP Replication Server detected loss for a primary SAP Replication Server or database. User transactions from the primary SAP Replication Server or database are no longer accepted. If the replication system has more than one SAP Replication Server, then the detected data loss may be either a Data Server Interface (DSI) loss or an Replication Server Interface (RSI) loss. If the replication system has only one SAP Replication Server, the detected data loss is a DSI loss. A DSI loss means that data was not replicated from the SAP Replication Server to the replicate database. An RSI loss means that data was not replicated from one SAP Replication Server to another SAP Replication Server.

Solution

For information on correcting data losses, see the Administration Guide Volume 2.

To prevent data loss, use DSI or RSI save intervals to create a backup strategy with logs large enough to keep all messages.