The Mirror Replication Agent instance must be running in Admin state to remove its objects from the primary database and to deinitialize Mirror Replication Agent. See “Starting Mirror Replication Agent” for more information.
Removing Mirror Replication Agent objects from
the primary database
Log in to the Mirror Replication Agent instance with the administrator login.
Use the ra_helpsysinfo command to verify that the Mirror Replication Agent objects exist in the primary database:
ra_helpsysinfo
When you invoke the ra_helpsysinfo command, Mirror Replication Agent returns a list of the transaction log base objects in the primary database if initialization completed successfully. If no information is returned, the transaction log does not exist in the primary database.
Use the pdb_setreptable command to disable replication for all marked tables in the primary database:
pdb_setreptable all, disable
When you invoke the pdb_setreptable command with the all and disable keywords, Mirror Replication Agent disables replication for all marked tables in the primary database.
Use the pdb_setrepproc command to disable replication for all marked procedures in the primary database:
pdb_setrepproc all, disable
Use the pdb_setreptable command to unmark all marked tables in the primary database:
pdb_setreptable all, unmark
When you invoke the pdb_setreptable command with the all and unmark keywords, Mirror Replication Agent removes replication marking from all marked tables in the primary database.
Use the pdb_setrepproc command to unmark all marked procedures in the primary database:
pdb_setrepproc all, unmark
When you invoke the pdb_setrepproc command with the all and unmark keywords, Mirror Replication Agent removes replication marking from all marked procedures in the primary database.
Normally, if any objects in the primary database are
marked for replication, you cannot remove the Mirror Replication
Agent transaction log.
Use the ra_deinit command to remove Mirror Replication Agent objects:
ra_deinit force
If the log removal script executes successfully, the script is stored in a file named partdeinit.sql file in the MA-15_2\inst_name\scripts\xlog\installed directory.
If the log removal script does not execute successfully, the script is stored in a file named partdeinit.sql in the MA-15_2\inst_name\scripts\xlog directory.
