Use of Oracle Home Path Variables
Starting with Enterprise Manager 13.5 Release 15 (13.5.0.15) you can use predefined variables for an Oracle Home path, simplifying your EM CLI and REST API Fleet Maintenance operations.
The following is a list of variables available in Enterprise Manager 13.5 for Oracle Home path definitions. You can specify variable name using the format %<variable name>%
.
Table 18-1 Variable definitions for Oracle Home Path
Variable | Implementation | Comments |
---|---|---|
ORACLE_BASE |
Oracle Base location for the Database.
Examples:
|
The Oracle Grid Infrastructure Oracle base should not contain the Oracle Grid Infrastructure binaries for an Oracle Grid Infrastructure for a cluster installation. Permissions for the file path to the Oracle Grid Infrastructure binary home are changed to root during installation. |
OH_PARENT_DIR |
Parent directory of the Oracle Home
Examples:
|
Computed after retrieving the Oracle Home location for the target from EM repository using the property name OracleHome .
|
VERSION |
The VERSION variable will be replaced with Oracle Database base release value.
Examples:
|
N/A |
VERSION_NAME |
The VERSION_NAME variable will be replaced with Version Name value of that Image.
Note: This is a mandatory input while creating an image.Examples:
|
N/A |
U |
This optional variable allows you to install the same product more than once in the same Oracle base directory.
Examples:
|
This variable is to be used only for bulk deployment. It is recommended to use this variable when there are several Oracle Homes in the same environment allowing you to update all in a single go.
Note: Multiple Home deployment in parallel on the same host is currently not supported for Windows based Enterprise Manager Deployments |
Note:
For security purposes, the Oracle Home or Grid Home path folder should not contain binaries and data files of the existing home.Table 18-2 Support for Variables in the Working Directory
Variables | Implementation | Comments |
---|---|---|
emStageDir |
You can manually update the agent property file with the following commands: from
|
N/A |