Closes the current Oracle Rdb monitor log file, compresses it,
    and opens another one without stopping the monitor.

1  –  Description

    The RMU Monitor Reopen_Log command closes the current Oracle
    Rdb monitor log file, compresses it, and opens another log file
    without stopping the monitor. The new log has the same name as,
    but a new version number of, the monitor log file you opened with
    the RMU Monitor Start command. Use the RMU Show Users command to
    determine the current name and location of the monitor log file
    before issuing the RMU Monitor Reopen_Log command. You should use
    the RMU Monitor Reopen_Log command if the monitor log file gets
    too large. For example, if you are running out of space on your
    disk or if database performance slows, you might want to open
    another log file.

    If the disk that contains the Oracle Rdb monitor log file
    becomes full, you must acquire space on the disk. Once there
    is sufficient space on this disk, use the RMU Monitor Reopen_Log
    command and consider backing up (using the DCL COPY command or
    the OpenVMS Backup utility) the old monitor log file.

    When the disk that contains the monitor log becomes full, Oracle
    Rdb stops writing to the log file, but the Oracle Rdb system
    does not stop operating. A message is sent to the cluster system
    operator when this occurs.

2  –  Format

  (B)0   RMU/Monitor Reopen_Log

3  –  Usage Notes

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

4  –  Examples

    Example 1

    The following example closes the existing monitor log file,
    compresses it, and creates a new one without stopping the Oracle
    Rdb monitor:

    $ RMU/MONITOR REOPEN_LOG

    See the Oracle Rdb Guide to Database Maintenance for more
    examples that show the RMU Monitor commands.