o  The database administrator requires RMU$ALTER privilege to run
       the command and the Rdb server also requires SELECT and ALTER
       privilege on the database.

    o  This command supersedes the RMU Repair Initialize=Larea_
       Parameters command that can also change the Thresholds and
       Length for a logical area. This command can be executed
       online, whereas the RMU Repair command must be run offline.

    o  Wildcard names are not permitted with the following qualifiers
       to prevent accidental propagation of values to the wrong
       database objects.

       -  LENGTH qualifier with a value specified,

       -  RENAME_TO qualifier,

       -  and THRESHOLDS qualifier.

    o  RMU Set AIP may be used on a master database configured for
       HOT STANDBY. All AIP changes and SPAM rebuild actions are
       written to the after image journal and will be applied to the
       standby database. This command cannot be applied to a STANDBY
       database.

    o  THRESHOLDS for MIXED format areas are physical area attributes
       and are not supported at the logical area (aka AIP) level.
       Therefore, THRESHOLDS can not be applied to MIXED areas and
       specifying logical areas will cause an exception to be raised.

    o  The REBUILD_SPAMS qualifier is only applied to logical areas
       stored in UNIFORM page format storage areas.

    o  This command will implicitly commit any changes with no
       opportunity to undo them using rollback. Access to the
       functionality is controlled by privileges at the RMU and Rdb
       database level. We suggest that RMU Show AIP be used prior to
       any change so that you can compare the results and repeat the
       RMU Set AIP command with corrections if necessary.

       Some wildcard operations are restricted to prevent accidental
       damage to the database. For instance, a wildcard matching
       many objects will be rejected if more than one type of object
       is being changed. If a wildcard selects both table and index
       types then this command will be rejected.

    o  This command is an online command. Each logical area will be
       processed within a single transaction and interact with other
       online users.

    o  When the AIP entry is changed online, any existing users of
       the table or index will start to use the new values if the
       logical areas are reloaded.

    o  Various SQL alter commands will register changes for the AIP
       and these are applied at COMMIT time. RMU Verify and RMU Show
       AIP Option=REBUILD_SPAMS will report any logical areas that
       require SPAM rebuilding. The database administrator can also
       examine the output from the RMU Dump Larea=RDB$AIP command.

    o  How long can the SPAM rebuild be delayed? The fullness of
       some page will have been calculated using the old AIP length
       or THRESHOLD values. Therefore, it might appear that a page
       is full when in fact the revised length will fit on the
       page, or the page may appear to have sufficient free space
       to store a row but once accessed the space is not available.
       By rebuilding SPAM pages, you may reduce I/O during insert
       operations. However, delaying the rebuild to a convenient time
       will not affect the integrity of the database.

    o  The amount of I/O required for Rebuild_Spams depends upon
       the number of pages allocated to the table or index involved.
       Assuming just one logical area is selected then Oracle Rdb
       will read the ABM (Area Bitmap) to locate all SPAM pages in
       that area that reference this logical area. Rdb will then
       read each page in the SPAM interval for that SPAM page and
       recalculate the fullness based on the rows stored on each
       page.