Quiet_Point
    Noquiet_Point

    Allows you to specify that a database copy 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.

    When you specify the Noquiet_Point qualifier, Oracle RMU proceeds
    with the copy operation as soon as the RMU Copy_Database command
    is issued, regardless of any update transaction activity in
    progress in the database. Because Oracle RMU must acquire
    concurrent-read locks on all physical and logical areas, the
    copy operation fails if there are any active transactions with
    exclusive locks on a storage area. However, once Oracle RMU 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 copy operation is proceeding, that transaction either
    waits or gets a lock conflict error, but the copy operation
    continues unaffected.

    If you intend to use the Noquiet_Point qualifier with a copy
    procedure that previously specified the Quiet_Point qualifier
    (or did not specify either the Quiet_Point or Noquiet_Point
    qualifier), you should examine any applications that execute
    concurrently with the copy operation. You might need to modify
    your applications or your copy procedure to handle the lock
    conflicts that can occur when you specify the Noquiet_Point
    qualifier.

    When you specify the Quiet_Point qualifier, the copy operation
    begins when a quiet point is reached. Other update transactions
    issued after the database copy operation begins are prevented
    from executing until after the root file for the database has
    been copied (copying of the database storage areas begins after
    the root file is copied).

    The default is the Quiet_Point qualifier.