Output=log-filename.out
    Output=log-filename_pid.out

    Identifies the name of the file where you want the Hot Standby
    software to create an operational output file (log) for the LCS
    or LRS process:

    o  Specify the Output qualifier on the master database to create
       an output file and collect information about the LCS process.

    o  Specify the Output qualifier on the standby database to create
       an output file and collect information about the LRS process.

    o  Optionally, include "_PID" or "_pid" when you specify the
       output file name. This causes the software to create a unique
       file name because it includes the process identification (PID)
       number.

    Applicable to:              Master and standby databases
    Required or Optional:       Optional
    Default Value:              None. If you do not specify the
                                Output qualifier, the Hot Standby
                                software does not record LCS or LRS
                                process activities to an output file.

    The Output qualifier overrides definitions you make with the
    BIND_LCS_OUTPUT_FILE or BIND_LRS_OUTPUT_FILE logical name. If you
    enable replication operations for multiple databases, there will
    be multiple operational output files.

    The purpose of the operational log is to record the transmittal
    and receipt of network messages, and to provide administrative
    and diagnostic information.

    Note the following when you specify the Output qualifier:

    o  You must specify an output file name. When you include "_PID"
       in the output file specification, the command creates a unique
       file name that includes the process identification (PID).

       This command line creates a unique file name, for example,
       DISK1:[USER]LRS_25C02914.OUT.

    o  Do not include a node name designation when you specify the
       output file name.

    o  The default location is the database root file directory. You
       can optionally include a directory name when you specify a
       file name.

    o  The directory containing the output files must be readable and
       writable by all processes.

    o  The default file type is .out

    o  You can display the name of output files that you specify with
       the Output qualifier using the RMU Show Users command (shown
       in Example 7-1). Output file names are not displayed in Show
       Users output for files specified with a logical name.

                                      NOTE

          All bugcheck dumps are written to a corresponding
          bugcheck dump file. Bugcheck dumps are not written to
          the Output operational log.

    Although it is optional, Oracle Corporation recommends that
    you use the Output qualifier, or a logical name, to collect
    information about the LCS and LRS processes during replication.

    You can also collect information about the ABS, ALS, DBR, and
    AIJSERVER processes by defining a logical name. The following
    table lists the logical names you can define to collect server
    process information to an output file:

    Logical Name           Specifies an output file for the . . .

    BIND_ABS_LOG_FILE      ABS process
    BIND_ALS_OUTPUT_FILE   ALS process (1)
    BIND_DBR_LOG_FILE      DBR process
    BIND_HOT_OUTPUT_FILE   AIJSERVER process
    BIND_LCS_OUTPUT_FILE   LCS process
    BIND_LRS_OUTPUT_FILE   LRS process

    Footnote (1):
    You can also collect information about the ALS process to an
    output file by including the Output qualifier on the RMU Server
    After_Journal command. For more information about displaying ALS
    information, refer to the Oracle RMU Reference Manual.

    Defining a logical name is also useful if you omitted the Output
    qualifier when you entered the Replicate After_Journal Start
    command to start replication. You can define a logical name to
    specify an output file while replication operations are active.
    This can be done by defining the appropriate logical name, and
    then invoking the Replicate After_Journal Reopen_Output command.
    This allows you to create an output file so the server can start
    writing to the file without you having to stop and start the
    server.