Confirm[=options]
    Noconfirm

    Specifies whether or not the RMU /RECOVER command causes the
    operator to be queried when an incorrect sequence of AIJ files is
    detected.

    The default for interactive recoveries is /CONFIRM, which
    prompts the user to see if he wants to continue. The default
    for RMU/RECOVER/NOCONFIRM and RMU/RECOVER executed in batch
    jobs is to terminate the RMU/RECOVER at the point where
    the out of sequence AIJ file is detected (equivalent to
    RMU/RECOVER/CONFIRM=ABORT).

    To override the default behavior, the user can continue to roll
    forward and ignore the missing AIJ file either by specifying the
    command syntax RMU/RECOVER/CONFIRM to get a prompt on whether to
    continue rolling forward if there is an AIJ sequence gap, or by
    specifying the syntax RMU/CONFIRM=CONTINUE if he does not want
    the prompt or is executing the RMU/RECOVER in a batch job.

                                   NOTE

       Oracle recommends that, in general, an incorrect journal
       sequence not be applied as a corrupt database may result.

    The /Order_Aij_Files qualifier can be used to help ensure that
    the specified journals are applied in the correct order.

    The Confirm qualifier accepts the following options:

    o  CONFIRM=CONTINUE

       Do not prompt the user if a sequence gap is detected on the
       next AIJ file to be rolled forward but ignore the missing AIJ
       file and continue rolling forward.

    o  CONFIRM=ABORT

       Do not prompt the user if a sequence gap is detected on
       the next AIJ roll forward but end the database recover at
       this point. This is the same as the default behavior for
       RMU/RECOVER/NOCONFIRM and RMU/RECOVER in batch.