User`s guide
Starting Oracle Utilities in the POSIX environment
Getting Started 1-5
Set the variable
ORACLE_SID
to start an Oracle utility for a specific Oracle instance.
Additional instance-specific parameters that are defined in the related BS2000
ORAENV
file, may be set in the POSIX environment or by accessing the BS2000
ORAENV
file.
Utilities running in the POSIX shell provide the opportunity to read instance-specific
variables from the
ORAENV
file in the BS2000 file system. To provide access to the
BS2000
ORAENV
file, you must create a file named
oraenvsid
in the
oracle_home_
path/dbs
directory. This file contains the full qualified BS2000 filename of the BS2000
ORAENV
file. It acts like a link to the
ORAENV
file in the BS2000 file system.
For example, if you want to access the
ORAENV
file
$ORADATA.ORCL.P.ORAENV
, then you
must create a
oraenvORCL
file in the
oracle_home_path/dbs
directory as follows:
$ ORACLE_HOME=/u01/app/orac1120/product/dbhome
$ export ORACLE_HOME
$ echo '$ORADATA.ORCL.P.ORAENV' > $ORACLE_HOME/dbs/oraenvORCL
$ chmod 664 $ORACLE_HOME/dbs/oraenvORCL
If an Oracle utility uses the BEQ protocol to connect to a database, then Oracle Net
Services will get the job parameters for the start of a dedicated server in the BS2000
environment from the
BGJPAR
variable. If this variable is not specified, then Oracle Net
Services will use default values.
While using the BEQ protocol, it is recommended that particular BS2000 job
parameters are defined for BS2000 jobs started by Oracle Net Services. The
BGJPAR
variable provides the option to define these parameters. You can define this variable
either in the related BS2000
ORAENV
file or by explicitly setting it in the POSIX
environment to the appropriate value.
For example, if a bequeathed server task should be assigned to a special
JOB-CLASS
,
then set the
BGJPAR
variable in the POSIX environment as follows:
$ ORACLE_SID=orcl
$ export ORACLE_SID
$ BGJPAR='START=SOON,CPU-LIMIT=NO,JOB-CLASS=JCBORA,LOGGING=*NO'
$ export BGJPAR
You can start the utilities in the same way as on other UNIX systems, such as for
SQL*Plus, using the following commands:
$ sqlplus /nolog
Note:
■ Utilities running in the POSIX shell handle the variables of the
BS2000
ORAENV
file as subordinated variables.Environment
variables in the POSIX shell take precedence over settings in the
BS2000
ORAENV
file.
■ The
SID
in the filename
oraenvsid
is case sensitive and must
match the
SID
specified in
ORACLE_SID
.
■ You must grant access for all users to the BS2000
ORAENV
file, if the
POSIX user that runs the Oracle utility in the POSIX shell is
different from the BS2000 user ID where the
ORAENV
file is located.
Note: The
BGJPAR
variable is not set after running the
oracle_home_
path/.profile.oracle
profile.