Oracle environment file

A number enclosed in single quotation marks and preceded by the letter X is interpreted as a hexadecimal number. These variables specify the user ID and sid of the file for the background enter jobs. If you want to use a special enter job file, then the parameters must be set to the desired userid and sid. This variable specifies whether the operating system message that a new job was accepted should be logged on SYSOUT or not.

Syntax: sid is a string of a maximum of 4 alphanumeric characters. This variable specifies the BS user ID where the instance identified by sid resides. This parameter specifies the identification of the shared code pool of the Oracle database instance for some common Oracle Database software components. This parameter specifies the address of the shared code pool of the Oracle database instance for some common Oracle Database software components.

This variable is used internally in identifying the background tasks and generating task-specific names. You must never specify values for this variable. This variable specifies the base address of the shared memory pool for the Oracle Database kernel module.

This must be an integral number of megabytes. The Oracle home directory is the directory in the POSIX file system, which contains the installation of the software for a particular Oracle product. 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 64 KB boundary. This variable specifies the size of the fixed part of the PGA.

This variable must not be changed from its default value. This variable specifies the physical blocksize of redo log files. This variable specifies the base address of the shared memory pool for the SGA of an Oracle Database instance. The base address must lie on a megabyte boundary. This variable provides a default host string for connect requests where no host string is specified. If you connect to the same database always, then it may be convenient to specify this variable. This value must contain everything you would otherwise specify after the " " character.

This variable deactivates the signal routine for user interrupts, which sends a break over the network. An interrupt can be released by pressing the [K2] key. This variable specifies the time a parent process waits until it establishes a connection to a child process. This variable specifies the identification of the shared memory pool for the client-side shared code of Oracle Database, which is used by customer written database applications.

This variable specifies the scope of the shared memory pool for the client-side shared code of Oracle Database, which is used by customer written database applications.

The valid values are:. All Oracle Database client tasks within the same BS user ID as the calling task are participants of the shared memory pool.

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 is useful when many users are sharing a single BS user ID. Default: userid. This variable defines the database that is used if no database identification is given at connect time. 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.

Elements of the path are separated by semicolons ;. For example:. 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.

To ensure that the variables are consistent, Oracle recommends that database startup and shutdown, background tasks, and server tasks refer to the same ORAENV file. The default values listed in the following sections are built-in defaults, some of them are overridden by settings in the shipped DEMO.

Address and Size Specification. Several variables described in this section define memory addresses and sizes. The notations used to specify these items are as follows:. A number enclosed in single quotation marks and preceded by the letter X is interpreted as a hexadecimal number. These variables specify the user ID and sid of the file for the background enter jobs. If you want to use a special enter job file, then the parameters must be set to the desired userid and sid.

This variable specifies whether the operating system message that a new job was accepted should be logged on SYSOUT or not. Syntax: sid is a string of a maximum of 4 alphanumeric characters. This variable specifies the BS user ID where the instance identified by sid resides. This parameter specifies the identification of the shared code pool of the Oracle database instance for some common Oracle Database software components.

This parameter specifies the address of the shared code pool of the Oracle database instance for some common Oracle Database software components. The same principle applies to all directories, apart for the admin directory. Product files include forms files, reports files, and files used to upgrade the database.

To display data entry forms for Oracle General Ledger, for example, Oracle E-Business Suite accesses files in the forms subdirectory under the The next figure expands the inset to show the full directory structure for gl. The following table summarizes product subdirectories and the types of files each one may contain.

Note: Not all products use all the subdirectories listed in this table. OBJ on Windows , with compiled code specific to one of the product's programs.

DLL on Windows , with compiled code common to the product's programs. These directories hold translated data, forms, and message files.

For example, the language directory named D designates German. The data loader files in the D subdirectory of the admin directory contain the German translation of the product seed data. The D directory in the forms directory contains the same forms, translated into German. However, the mesg directory contains message files in both American English and German. The admin, ad, au, and fnd directories are the core technology directories. This directory and its subdirectories contain files and scripts used by the AD utilities during upgrade and maintenance processes.

The adovars. The au Applications Utilities directory. This directory and its subdirectories contain product files that are consolidated in a single location for optimal processing. These files include:. A copy of all Java files used when regenerating the desktop client JAR files, in the java subdirectory. This directory and its subdirectories contain the scripts and programs that are used as the foundation for all Oracle E-Business Suite products to build data dictionaries, forms and C object libraries.

Rapid Install sets up this configuration as the default for nodes that are running the same operating system. These files make up the application tier file system, and can be shared across multiple application tier nodes provided they are running the same operating system.

Note: A shared file system configuration is currently not supported on application tier server nodes running Windows. With a shared application tier file system, all application tier files are installed on a single shared disk resource that is mounted from each application tier node. Any application tier node can then be used to provide standard services, such a serving forms or Web pages, or concurrent processing.

As well as reducing disk space needed, there are several other benefits of a shared application tier configuration:. Most administration, patching, and maintenance tasks need be performed only once, on a single application tier node. Capabilities for sharing the application tier file system were extended further in Release An application tier file system installed and configured in this way can be used to access two or more database instances.

Note: For further details of features, options, and implementation steps, see My Oracle Support Knowledge Document For details of shared application tier file system usage in the context of high availability, see Chapter 9.

Many of the parameters are specified during the install process. Running it creates a command window with the required environment settings for Oracle E-Business Suite. Some Oracle E-Business Suite utilities use your operating system's default temporary directory even if you define the environment settings listed in the previous paragraph. In a Release 12 environment, adovars.

AD utility programs perform a variety of database and file management tasks. These utilities need to know certain configuration information to run successfully. This configuration information is specified when Oracle E-Business Suite is installed, and subsequently stored in the adconfig.

Once it has been created, this file is used by other Oracle E-Business Suite utilities. Note: adconfig. It is distinct from the config. This file sets additional environment variables used by the Application Object Library. This file should not be modified: the default values are applicable for all customers.