Terminates database replication operations.

1  –  Description

    You can enter the command on either the master node or the
    standby node.

    When you enter the command on the master database, replication
    is terminated immediately. Active transactions are handled
    differently depending on whether you specify the Abort qualifier
    or take the default (Noabort).

    When you enter the command on the standby database, replication
    is terminated after any pending after-image journal records are
    completely rolled forward. Any active transactions on the standby
    database are rolled back.

    You can stop database replication while the master database,
    the standby database, or both databases are on line (open) and
    accessible for active use. There is no need to close either
    database to stop database replication.

    If the database is not manually opened on the node where you
    entered the Replicate After_Journal Start command, you must enter
    the Replicate After_Journal Stop command on the node where the
    corresponding replication server is running, or first open the
    database manually.

    When replication operations stop, the Hot Standby software
    automatically restarts the AIJ log server (ALS) processes on
    the standby node.

2  –  Format

  (B)0RMU/Replicate After_Journal Stop database-rootfile

  Command Qualifiers                   x Defaults
                                       x
  /[No]Abort[={Forcex | Delprc}]       x /Noabort
  /[No]Log                             x /Nolog
  /[No]Wait                            x /Wait

3  –  Parameters

3.1  –  database-rootfile

    Specifies the database root file for which you want to stop
    replication operations.

4  –  Command Qualifiers

4.1  –  Abort

    Abort=Forcex
    Abort=Delprc
    Noabort

    Indicates whether pending after-image journal information
    is rolled forward on the standby database before database
    replication operations are shut down. The following list
    describes the qualifiers:

    o  Abort=Delprc

       The Abort=Delprc qualifier closes the database, and recovery
       unit journals (RUJ) are not recovered. The processes and any
       subprocesses of all Oracle Rdb database users are deleted.

    o  Abort=Forcex

       The Abort=Forcex option closes the database, and recovery unit
       journals (RUJ) are recovered and removed.

    o  Abort

       When the Abort qualifier is specified without a keyword,
       database replication shuts down as quickly as possible.
       Any after-image journal information waiting to be rolled
       forward on the standby database is discarded, and all active
       transactions on the standby database are rolled back.

    o  Noabort (default)

       Database replication shuts down after all after-image journal
       information waiting to be rolled forward on the standby
       database is completed. Note that this type of shutdown could
       still result in active transactions being rolled back on the
       standby database.

4.2  –  Log

    Log
    Nolog

    Enables or disables logging the results of the Replicate After_
    Journal Stop operation.

    Applicable to:              Master and standby databases
    Required or Optional:       Optional
    Default Value:              Nolog

    If you specify the Log qualifier, the log file output is written
    to SYS$OUTPUT on OpenVMS.

4.3  –  Wait

    Wait
    Nowait

    Indicates whether or not the Replicate command should wait for
    activation of the replication server processes before returning
    control to the user.

    Applicable to:              Master and standby databases
    Required or Optional:       Optional
    Default Value:              Wait

    The Wait qualifier has the following effects:

    o  On the master database node-replication waits for deactivation
       of the server processes on the master database node

    o  On the standby database node-replication waits for
       deactivation of the server processes on the standby database
       node

    The following list describes the Wait and Nowait qualifiers:

    o  Wait (default)

       The Replicate command does not return to the user until
       the respective server process has successfully stopped the
       database replication operation. Replication waits indefinitely
       for the termination of the server process, even though
       termination might take substantial time. However, the server
       process might not actually stop the replication operation.

    o  Nowait

       Control should be returned to the user as soon as the LCS or
       LRS server process has been stopped by the database monitor.

                                   NOTE

       You must wait for commands that include the Nowait qualifier
       to complete before you enter another command. This is
       because if the first command fails before the subsequent
       command executes, the second command might receive the
       HOTCMDPEND error. For example:

       $ RMU/REPLICATE AFTER_JOURNAL START/NOWAIT mf_personnel
       $ RMU/REPLICATE AFTER_JOURNAL STOP/WAIT mf_personnel

       If the first command to start replication fails, the startup
       error might be returned to the waiting Replicate After_
       Journal Stop command.