User`s guide

User ID Requirements
Architecture and Implementation 2-9
2.6 The ORALOAD Library
The
ORALOAD
library (
$ORAC1120.ORALOAD.LIB
by default) is required to run any Oracle
Database 11g Release 2 program. The Oracle Database uses this library to load
executables and subroutines dynamically when required. The link name
ORALOAD
must
identify the
ORALOAD
library before calling any Oracle Database program. If the link
name is missing, then you get a
BLS (BS2000/OSD loader)
error message. Usually, this
link name is set when the
ORAENV
procedure is called.
2.7 The ORAMESG library
The
ORAMESG
library (
$ORAC1120.ORAMESG.LIB
) is required for dynamically loading
tables, such as message files, by an Oracle task when required. The link name
ORAMESG
must identify the
ORAMESG
library before calling any Oracle program. If the link name
is missing, then you get a
BLS (BS2000/OSD loader)
error message. Usually, this link
name is set when the
ORAENV
procedure is called.
2.8 User ID Requirements
Review the following sections to know about the user ID requirements.
Installation User ID (ORAUID)
DBA User ID
User IDs for Oracle users
2.8.1 Installation User ID (ORAUID)
During installation, the complete Oracle Database software is installed into this user
ID, which should be empty. This installation user ID (referred to as
ORAUID
) includes:
executable programs, such as SQL*Plus, the background and network programs.
load libraries, in particular,
ORALOAD.LIB
, from which modules are loaded during
program execution. For example, the shared KERNEL module, and the
precompiler run-time modules.
message files.
other data files, such as SQL file, for the
DEMO
tables.
the
INCLUDE
files, application demo files, and system configuration files specifying
default precompiler options for precompiler users.
object libraries required to link-edit precompiler applications, such as
PRO.LIB
.
port-specific installation utilities, such as programs, command procedures, and so
on.
default configuration files, such as the default
ORAENV
file.
Oracle installation in the POSIX file system.
A separate
ORAUID
is required for each separate Oracle Database release. However,
multiple databases using the same version can, and should, refer to the same
installation user ID.
2.8.1.1 Authorizations and File Access Rights
This user ID does not require any special BS2000 privileges.