Stops the Oracle Rdb monitor process.

1  –  Description

    The RMU Monitor Stop command stops the Oracle Rdb monitor process
    (RDMS_MONITORnn, where nn represents the version Oracle Rdb)
    normally, either with a shutdown and rollback of the databases or
    an immediate abort. You can use the RMU Monitor Stop command
    to shut down all database activity on your node, optionally
    aborting user processes by forcing an image exit or deleting
    their processes.

    The RMU Monitor Stop command closes the monitor log file also.

    An Oracle Rdb monitor process must be running on a node for
    users logged in to that node to use any Oracle Rdb database.
    In a VMScluster environment, a monitor process must be running on
    each node in the cluster from which databases is accessed.

    The Oracle Rdb monitor process controls all database access and
    initiates the automatic database recovery procedure following a
    system failure or other abnormal termination of a database user
    process. The monitor log file automatically tracks all access to
    the database.

2  –  Format

  (B)0   RMU/Monitor Stop

     Command Qualifiers                 x Defaults
                                        x
     /[No]Abort[={Forcex | Delprc}]     x /NOABORT
     /[No]Wait                          x /NOWAIT

3  –  Command Qualifiers

3.1  –  Abort

    Abort=Forcex
    Abort=Delprc
    Noabort

    The Abort=Forcex qualifier stops the monitor immediately without
    allowing current Oracle Rdb users to complete active transactions
    or detach from their databases. However, the user processes are
    not deleted. Active transactions are rolled back. If a process
    using a database is waiting for a subprocess to complete, the
    transaction is not rolled back until the subprocess completes.
    Using the Abort qualifier with no option is equivalent to
    specifying the Abort=Forcex qualifier.

    The Abort=Delprc qualifier stops the monitor immediately without
    allowing current Oracle Rdb users to complete active transactions
    or detach from their databases. Each user process that was
    attached to an Oracle Rdb database is deleted immediately.

    The Noabort qualifier allows current user processes to continue
    and complete before stopping. New users on the node are not
    allowed to attach to any database, but existing database users
    can complete their sessions normally. Once existing database user
    processes terminate, the database monitor shuts down.

    The Noabort qualifier is the default.

3.2  –  Wait

    Wait
    Nowait

    Specifies whether the Oracle RMU operation completes when the
    monitor acknowledges the stop request (Nowait), or whether RMU
    waits until the monitor finishes shutting down (Wait).

    The default is Nowait.

4  –  Usage Notes

    o  To use the RMU Monitor Stop command, you must have either the
       OpenVMS SETPRV privilege or the OpenVMS WORLD, CMKRNL, DETACH,
       PSWAPM, PRMMBX, ALTPRI, SYSGBL, SYSNAM, SYSPRV, and BYPASS
       privileges.

                                      NOTE

          If Oracle Trace is installed on your system, you stall
          the Oracle Rdb monitor process with the RMU Monitor Stop
          command unless you do one of the following:

          -  Shut down Oracle Trace, then shut down the Oracle Rdb
             monitor (in that order).

          -  Use the RMU Monitor Stop command with the Abort=Delprc
             qualifier to shut down Oracle Rdb and force the
             monitor out of the Oracle Trace database.

5  –  Examples

    Example 1

    The following command causes the Oracle Rdb monitor process to
    shut down after existing database users end their access to the
    database. New users on this node are unable to attach to any
    Oracle Rdb database.

    $ RMU/MONITOR STOP

    Example 2

    The following command causes the Oracle Rdb monitor to stop
    immediately without allowing current Oracle Rdb users to
    complete active transactions (they are rolled back) or detach
    (DISCONNECT) from their databases. However, the user processes
    are not deleted. Because the monitor is shut down, all Oracle Rdb
    activity on this node is terminated.

    $ RMU/MONITOR STOP /ABORT=FORCEX

    Example 3

    The following command causes the Oracle Rdb monitor to stop
    immediately without allowing current Oracle Rdb users to
    complete active transactions (they are not rolled back) or
    detach (DISCONNECT) from their databases. Each user process that
    was attached to a Oracle Rdb database on this node is deleted
    immediately.

    $ RMU/MONITOR STOP /ABORT=DELPRC