If insert or update operations in the primary database are not being replicated, and if you do not find any errors in the Mirror Replication Agent system logs, the most likely cause of the problem is that the value of the origin queue ID (qid) sent to the Replication Server is lower than previous values of the qid. In that case, the new operations are ignored by Replication Server.
To correct the problem of incorrect qid values
Turn on tracing for the Mirror Replication Agent LTITRACELTL trace flag.
You can view Mirror Replication Agent LTL output by examining the contents of the LTITRACELTL.log file.
Log in to the Replication Server and use the admin who, sqm command to determine if any duplicate operations are in the inbound queue of the Replication Server.
If you find duplicate operations in the inbound queue of the Replication Server, then Mirror Replication Agent is re-sending operations to the Replication Server as part of a recovery process. Finding duplicate operations indicates that the value of the Mirror Replication Agent origin queue ID is not the problem.
If you find no duplicate operations in the inbound queue of the Replication Server, continue this procedure to reset the qid value.
Log in to the Mirror Replication Agent administration port.
Use the Mirror Replication Agent quiesce command to put the Mirror Replication Agent instance in Admin state.
quiesce
Use the Mirror Replication Agent ra_locator command to set the value of the LTM Locator stored in the RASD to all zeros.
ra_locator zero
Log in to the RSSD and execute the rs_zeroltm stored procedure.
rs_zeroltm pds, pdb
where:
pds is the name of the primary data server.
pdb is the name of the primary database, as specified in the Replication Server create connection command.
Restart replication using the Mirror Replication Agent resume command.
resume
When the value of the LTM Locator is set to all zeros in both the RASD and the RSSD, Mirror Replication Agent starts scanning the transaction log at the end of the log.
