Quiet_Point
    Noquiet_Point

    Allows you to specify that a database move 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 move operation as soon as the RMU Move_Area command is
    issued, regardless of any update transaction activity in progress
    in the database. Because Oracle RMU must acquire exclusive locks
    on the physical and logical areas for the areas being moved,
    the move operation fails if there are any active transactions
    with exclusive locks on storage areas that are being moved.
    However, once Oracle RMU has successfully acquired all the needed
    concurrent-read storage area locks, it should not encounter any
    further lock conflicts. If a transaction is started that causes
    Oracle Rdb to request exclusive locks on the areas that are in
    the process of being moved, that transaction either waits or
    gets a lock conflict error, but the move area operation continues
    unaffected.

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

    When you specify the Quiet_Point qualifier, the move operation
    begins when a quiet point is reached.

    The default is Quiet_Point.