Step 6. Reset the primary Oracle database for replication

In a test environment, there may be times when the replication environment should be reset. Instead of deleting and re-creating a new MRO instance, use the following procedure to facilitate resetting the environment.

StepsTo reset the primary Oracle database for replication

  1. Protect your new environment from old log information by using the following command in MRO to archive all current redo log data:

    	pdb_init move_truncpt
    

    Or, use the Oracle command:

    	SQL> alter system archive log current ;
    
  2. To retain marking and log device information, re-initialize the MRO using ra_init with the force option, which forces the MRO repository to be refreshed instead of overwritten:

    ra_init force
    

    NoteIf you prefer to delete and replace all the information in the MRO repository, issue the ra_deinit command followed by a normal ra_init command (without the force option):

    For more information about the ra_init command, see the Mirror Replication Agent Reference Manual.

  3. If you adjust or zero-out the locator stored in Rep Server, the following is an example of a rs_zeroltm command:

    isql -USAMPLE_RS_RSSD_prim -PSAMPLE_RS_RSSD_prim_ps -SSAMPLE_RS_ERSSD -DSAMPLE_RS_ERSSDrs_zeroltm NY, NYora92
    
    go
    

    The following is displayed:

    Locator has been reset to zero.(return status = 0)