User`s guide

User ID Requirements
2-10 Oracle Database Installation and Administration Guide
■ You must not use the BS2000/OSD System Administrator user ID TSOS as an
Oracle Database installation user ID.
■ The ORAUID does not require any specific user attributes or privileges.
■ Only the installation phase requires a BS2000 LOGIN under this user ID.
■ During installation all files are created with the file attributes:
USER-ACC=ALL-USERS, ACCESS=READ
■ You do not need to define write access for any file after installation.
■ The installation in the POSIX file system requires a unique user number and group
number for the installation user ID.
2.8.1.2 Default Name
The default name for the ORAUID is $ORAC1120 . If you install Oracle Database 11g
Release 2 under a different installation user ID, then the installation procedure changes
the default value to the current installation user ID in all related files.
2.8.2 DBA User ID
The DBA user ID is a BS2000 user ID that is used as the owner of one or more Oracle
databases. All the files for a specific Oracle database are owned by this user ID.
All tasks making up the running database, background tasks, and server tasks started
for two-task Oracle Database, execute under the
DBA user ID. These tasks refer to the
executable programs and libraries, which are available under the installation user ID
(
ORAUID ). These programs and libraries need not, and should not be copied into the
DBA user ID. It is possible to use the installation user ID (
ORAUID ) as a DBA user ID.
However, it is recommended that you use separate user IDs. The
DBA user ID can also
be used as a normal user ID.
Multiple databases can be created under the same, or under different DBA user IDs. If
installed under different BS2000 user IDs, then the databases are separated and
protected from each other, subject to the BS2000 protection mechanisms. In particular,
a Database Administrator cannot administer a database running under a different
BS2000 user ID (there is no global
DBA privilege in Oracle Database for BS2000/OSD).
2.8.2.1 Authorizations and File Access Rights
The DBA user ID needs specific user attributes and privileges to run an Oracle
Database. These privileges include:
■ the right to start jobs immediately, preferably in a JOBCLASS reserved for Oracle
Database background jobs. Failure to do this may cause delays when starting the
database and when spawning server tasks.
■ the right to start jobs with no time limit ( TIME=NTL ). Failure to do this may cause
database tasks to terminate.
■ the right to set jobs to TP state. Failure to do this may reduce database
performance.
■ the right to set Common Memory Pools as read-only. Failure to do this may reduce
shared-code security.
■ the BS2000/OSD System Administrator user ID TSOS should not, under any
circumstances, be used as an Oracle Database
DBA user ID.
■ file access rights set under the DBA user ID should be: