If the value of the use_rssd configuration parameter is true, Mirror Replication Agent connects to the RSSD to retrieve replication definitions for the primary database whenever the resume command is invoked.
In this section, the term replication definition refers
to both table replication definitions and function replication definitions.
Each time it retrieves replication definitions, Mirror Replication Agent stores that information in a cache. Mirror Replication Agent uses the replication definitions stored in its cache when generating LTL to send to the Replication Server.
If the Log Transfer Interface component encounters an operation for a database object that it does not have cached information for, Mirror Replication Agent reconnects to the RSSD to update its replication definition cache. If a replication definition cannot be found for the operation, the Log Transfer Interface generates unoptimized LTL for that operation, without the benefit of the replication definition, and continues operating normally.
If you drop a replication definition after Mirror Replication Agent has cached the RSSD information, a problem may occur. If the replication definition is dropped and then re-created, the Replication Server may suspend the Mirror Replication Agent connection when it receives LTL that is not formatted correctly for the object, as specified in the current replication definition in the RSSD.
To avoid this problem, you must:
Quiesce the Mirror Replication Agent instance.
Change the replication definition in Replication Server.
Resume the Mirror Replication Agent so that it has the correct version of the replication definition in its cache.
