Quiet_Point
    Noquiet_Point

    Allows you to specify that the database backup operation is to
    occur either immediately or when a quiet point for database
    activity occurs. A quiet point is defined as a point where no
    active update transactions are in progress in the database.
    Therefore, this qualifier is used with the Online qualifier.

    When you specify the Noquiet_Point qualifier, RMU Backup proceeds
    with the backup operation as soon as the RMU Backup command is
    issued, regardless of any update transaction activity in progress
    in the database. Because RMU Backup must acquire concurrent-
    read locks on all physical and logical areas, the backup
    operation will fail if there are any active transactions with
    exclusive locks on a storage area. However, once RMU Backup has
    successfully acquired all concurrent-read storage area locks it
    should not encounter any further lock conflicts. If a transaction
    that causes Oracle Rdb to request exclusive locks is started
    while the backup operation is proceeding, that transaction will
    either wait or receive a lock conflict error, but the RMU Backup
    command will continue unaffected.

    See the Usage_Notes help entry under this command for
    recommendations on using the Quiet_Point and Noquiet_Point
    qualifiers.

    The default is the Quiet_Point qualifier.