o  To use the RMU Repair command for a database, you must have
       the RMU$ALTER privilege in the root file access control
       list (ACL) for the database or the OpenVMS SYSPRV or BYPASS
       privilege.

    o  Enable detected asynchronous prefetch to achieve the best
       performance of this command. Beginning with Oracle Rdb V7.0,
       by default, detected asynchronous prefetch is enabled. You
       can determine the setting for your database by issuing the RMU
       Dump command with the Header qualifier.

       If detected asynchronous prefetch is disabled, and you do not
       want to enable it for the database, you can enable it for your
       RMU Repair operations by defining the following logicals at
       the process level:

       $ DEFINE RDM$BIND_DAPF_ENABLED 1
       $ DEFINE RDM$BIND_DAPF_DEPTH_BUF_CNT P1

       P1 is a value between 10 and 20 percent of the user buffer
       count.

    o  The Areas qualifier can be used with indirect file references.
       See the Indirect-Command-Files help entry.

    o  Oracle Corporation recommends that you use the RMU Backup
       command to perform a full backup operation on your database
       before using the RMU Repair command on the database.

    o  Use the SQL SHOW STORAGE AREA statement to display the new
       location of a snapshot (.snp) file and the RMU Dump command
       with the Header qualifier to display the new allocation.

    o  Be careful when you specify names for new .snp files with the
       RMU Repair command. If you specify the name of a file that
       already exists and was created for the database, it will be
       initialized as you requested.

       If you mistakenly initialize a live database file in this way,
       do not use the database until the error is corrected. Use the
       RMU Restore command to restore the database to the condition
       it was in when you backed it up just prior to issuing the RMU
       Repair command. If you did not back up the database before
       issuing the RMU Repair command, you must restore the database
       from your most recent backup file and then recover from .aij
       files (if the database had after-image journaling enabled).

       If you specify the wrong .snp file (for example, if you
       specify jobs.snp for all the .snp file name requests in
       Example 3 in the Examples help entry under this command),
       you can correct this by issuing the RMU Repair command again
       with the correct .snp file names.

       After the RMU Repair command completes, delete old .snp
       files and use the RMU Backup command to perform a full backup
       operation on your database.