Installation Procedure Requirements
Then grant the rights identifier to the Oracle9i account as follows:
UAF> GRANT/IDENTIFIER ORA_TEST_DBA ORACLE9i
If you add the ORA_TEST_DBA rights identifier, but grant only ORA_DBA to ORACLE9i, then the account would have insufficient privileges to administer the instance TEST.
The third line of the table shows that you can add and grant different identifiers, thereby restricting control of a particular instance while still granting control to other instances.
You can grant database maintenance privileges to accounts (for example, privileges to start up and shut down the database) in addition to the Oracle9i account. (However, with the Oracle9i account, the user UIC GROUP number must be greater than MAXSYSGROUP). By granting the ORA_<sid>_DBA identifier, you can similarly restrict user privileges to an instance named <sid>.
Process Rights for SGA Protection
Releases of the Oracle RDBMS on HP OpenVMS Alpha after Release 7.3.2.3.0 feature a change in the way that the software runs and accesses the SGA. Previous to Release 7.3.2.3.2, the SGA was protected by allowing only processes that are running in supervisor mode to access it directly. Starting with Release 7.3.2.3.2, the SGA is protected by an Access Control List to accommodate the kernel remaining in user mode.
Before bringing up a database, add a rights identifier to the User Authorization File (UAF). Have your system manager adhere to the following directions.
At the UAF> prompt, type:
UAF > ADD/IDENTIFIER/ATTRIBUTES=SUBSYSTEM ORA_SGA
Warning: DO NOT GRANT THE RIGHTS IDENTIFIER TO ANY USER. Oracle manages the assignment of the rights identifier when it starts the database.
