|Oracle9i Installation and Database Administration Guide
Release 2 (220.127.116.11.10) for Fujitsu Siemens Computers BS2000/OSD
Part Number B12034-01
This appendix describes each variable that can be specified in the ORAENV file.
The variables fall into the following three classes:
These variables are for database administration purposes. Most DBA variables are evaluated only during database startup.
These variables can be specified by ordinary users as well as by the DBA. When these variables are specified in a particular user's ORAENV file, they modify that user's environment only.
These variables apply to Oracle Net Services components. These variables should be included in the ORAENV file of the DBA.
The class (or classes) to which a variable belongs is noted in the variable descriptions in this appendix.
Any DBA or NET variables specified in an ordinary user's ORAENV file are ignored.
You should consider the following general rules when writing ORAENV files:
assigns the value $ORACL920.RDBMS.ADMIN to the variable SQLPATH. If ORAUID is changed, SQLPATH will automatically reflect the new value.
The following variables are always defined, and may be referenced in other variable assignments:
The LOGNAME variable always contains the current BS2000 userid. You cannot alter the value of this variable by assigning a different value to it in your ORAENV file.
This variable specifies the BS2000 userid where the Oracle Server programs, installation and demonstration files are installed. The initial value is derived from the ORALOAD linkname (the userid part of the ORALOAD library name). This value is usually correct, but if necessary, you can override it by assigning a different value to it in your ORAENV file.
The PGM variable always contains the last part of the current START_PROGRAM program name. You cannot alter the value of this variable by assigning a different value to it in your ORAENV file.
The TERM variable contains the terminal type, and defaults to 'SNI9750'. This default value is usually correct, but if necessary, you can override it by assigning a different value to it in your ORAENV file.
The TSN variable contains the task sequence number of the current task. You cannot alter the value of this variable by assigning a different value to it in your ORAENV file.
The variables described below are for general, day-to-day use by Oracle Server DBAs and users.
This variable provides a default host string for connect requests where no host string is specified. If you always connect to the same database, it may be convenient to specify this. This value should contain everything you would otherwise specify after the "@" character.
This variable should be set to FALSE when you use the Export utility to overcome a problem with the C library functions when an export file is written to tape.
This variable should be set to FALSE when you use the Import utility to overcome a problem with the C library functions when an import file is read from tape.
This variable is used by the Import utility for full database imports. When set to "Yes", the Import utility will strip the BS2000 userid from the tablespace filenames contained in the export dump file. This value must only be specified when importing full database exports created on a BS2000/OSD system.
This variable specifies the default language and character set. For example:
This variable is used for concatenation with the OS_AUTHENT_PREFIX see initialization parameter. The default value concatenates the value of the parameter OS_AUTHENT_PREFIX with the BS2000 userid. Using OPS_JID, you can specify that the BS2000 jobname (/.jobname LOGON...) is used instead. This is useful when many users are sharing one BS2000 userid.
This variable specifies the dump file for the Oracle Server and user trace output.
This variable defines the database that will be used if no database identification is given at connect time.
This variable specifies optional variables for the /PRINT command issued for SPOOL OUT spool files. Using this variable, the user can modify the spooled job, and, for example, route the job to a remote printer, add print options for laser printers, and so on. The BS2000 /PRINT command for spool files is issued as follows:
This variable specifies a path where SQL*Plus will look for command files. Elements of the path are separated by semicolons (;). For example:
This assignment will cause SQL*Plus to look for filename.SQL, then for PRIVATE.filename.SQL, and finally for $ORACL920.filename.SQL.
This variable specifies the password file for remote instance start. For further information, see Chapter 5, "Administering the Oracle Server".
The following variables are used during database and network startup. They supplement (and in some cases provide defaults for) variables contained in the initialization file.
We recommend that database startup and shutdown, background jobs, and network jobs should all refer to the same ORAENV file to ensure that the variables are consistent.
Note that the default values listed below are "built-in" defaults; most of them are over-ridden by settings in the shipped DEMO.P.ORAENV.
Several of the variables described in this section define memory addresses and sizes. The notation used to specify these items is as follows:
For example, the following all set the KNL_BASE variable to 8M:
This variable specifies if a precise method for handling of timeouts should be used. The parameter is important for RAC (see chapter "Real Application Cluster (RAC)").
This variable specifies the parameters for the ENTER-PROCEDURE command used when starting background jobs. The ENTER-PROCEDURE command is used to submit jobs as follows:
These variables specify the userid and orasid of the file for the background enter jobs. If the use of a special enter job file is desired, the parameters must be set to the desired userid and orasid.
This variable specifies whether the operating system message that a new job was accepted (i.e. an internal Oracle process, e.g. a listener) shall be logged on SYSOUT or not.
This variable specifies the parameters, which will be used by the ENTER-PROCEDURE command to start a server process for the instance specified by sid.
This variable specifies the USER-ID where the instance assigned by sid resides.
These parameters define credentials of a USER-ID, which will be used by the ENTER-PROCEDURE command to start a process.
user a string of at most 8 alphanumeric characters which
follows the rules of a BS2000/OSD USER-ID and must
match a USER-ID defined by the parameter sid_USER.
account a string of at most 8 alphanumeric characters which
follows the rules for a BS2000/OSD account number.
password a string of at most 8 alphanumeric characters which
follows the rules for a BS2000/OSD password.
This parameter specifies the identification of the the shared code pool for CORE, NLS, NET.
This parameter specifies the address of the shared code pool for CORE, NLS, NET.
This variable specifies if the instance can run in RAC mode (see chapter "Real Application Cluster (RAC)".
This variable is used internally in identifying the background tasks and generating task-specific names. You will see it in some places, but you should never specify it yourself.
This variable gives the base address where the shared memory pool is mapped in memory. This must be an integral number of megabytes.
This parameter specifies a directory in the POSIX file system which is used for installation and operation purposes of Java and Oracle Intelligent Agent (for more information see the chapters "Java in the Database" and "Oracle Intelligent Agent").
This variable specifies the base address of the fixed part of the PGA. The PGA is task-specific, but must be located at a fixed memory address so that the kernel can access it. The base address must lie on a 64Kb boundary.
This variable specifies the size of the fixed part of the PGA. This variable should not normally be changed from its default value.
This variable specifies the physical blocksize of redo log files.
This variable cannot be changed after database creation. Once you specify a value different from the default, you must specify it in all future calls.
This variable gives the address where the SGA is mapped into memory, and must represent a megabyte-boundary.
The value of SGA_BASE is read from the kernel if the shared kernel is already loaded. There is no corresponding SGA_SIZE variable; the size of the SGA memory pool is calculated when the database is started.
This variable, when set to 'Y', forces the size of the SGA to be rounded up to a whole number of megabytes. This may give some performance gain on certain hardware. Note that if the SGA is located above the 16Mb boundary, it is always rounded to next megabyte boundary.
This variable specifies the userid of the Oracle Net Services configuration files e.g. LISTENER.ORA, TNSNAMES.ORA and SQLNET.ORA. If TNS_ADMIN is not defined, the configuration files are searched under the local userid with the prefix NETWORK.ADMIN.
This variable specifies the time after which a connection between a parent and a child process is closed if there is no communication between them.
This variable forces the Oracle Net software to change always the server's IP-Node name to an IP-Node address.