o  This command requires exclusive database access (the database
       cannot be open or accessed by other users).

    o  Only one value can be supplied to the Rad_Hint qualifier. The
       indicated RAD must contain memory.

    o  When shared memory is set to System (with Galaxy enabled) or
       to Resident, then the process that opens the database must be
       granted the VMS$MEM_RESIDENT_USER identifier.

    o  For applications that can be partitioned into one or more
       RADs, the Rad_Hint qualifier allows additional control
       over exactly where memory for caches and global sections
       is allocated. This control can permit increased performance
       if all application processes run in the same RAD, and the
       database and row cache global sections also reside in that
       same RAD.

    o  When Resident shared memory is specified, the global demand-
       zero pages are always resident in memory and are not backed
       up by any file on any disk. The pages are not placed into the
       process's working set list when the process maps to the global
       section and the virtual memory is referenced by the process.
       The pages are also not charged against the process's working
       set quota or against any page-file quota.

    o  To save physical memory, Oracle Rdb generally attempts to
       create and use shared page tables when creating large resident
       global sections.