Settings | Functions |
---|---|
Name | Enter a name for the Oracle home. This name identifies the program group associated with a particular home and the Oracle services installed on this home. The Oracle home name must be between 1 to 127 characters long, and can include only alphanumeric characters and underscores. |
Software Location | Enter the full path to an Oracle home, or select an Oracle home from the drop-down list of existing Oracle homes. The Oracle home location is the directory where products are installed. Data files may or may not be installed within an Oracle home. You can use the Browse button to choose a directory to install your product. For Windows platforms, you must provide a valid path that is not in the Windows directory. Different homes cannot share the same location. |
installActions<timestamp>.log
file. Also, the Oracle Universal Installer aborts. To override this condition, use the -force
flag on the command line. The effect of using the -force
flag is the same as selecting Yes while installing in interactive mode. You receive a warning message, but the installation continues.ORACLE_HOME
name is taken first from the command line if it is specified, or else from the response file if specified. If not specified, the value of DEFAULT_ORACLE_HOME_NAME in oraparam.ini is examined. Typically, the following convention is used for the name:oraparam.ini
file; for example, 'Db11g', and <home_identifier>
is a counter derived from the Central Inventory. For example, the ORACLE_HOME
name could be OraDb11g_1
.ORACLE_HOME
environment variable is used. If neither is specified, the following conventions are used for the path:ORACLE_BASE
has been specified in the environment:$ORACLE_BASE/product/11.2.0/Db_1
.ORACLE_BASE
has not been specified in the environment:ORACLE_HOME
path could be $HOME/product/11.2.0/Db_1
.oradata
, flash_recovery_area
, admin
, and doc
directories are created under ORACLE_BASE
. If ORACLE_BASE
has not been specified, the default is the $ORACLE_HOME/oradata
directory. If the parent directory of the Oracle home is writable, these directories are created in the parent directory of the Oracle home.Platform | Default Inventory Pointer Location |
---|---|
Linux Linux.PPC64 AIX | /etc/oraInst.loc |
Solaris.SPARC Solaris.X64 HPUX HPIA HP.TRU64 Linux.IA64 Linux.xSeries | /var/opt/oracle/oraInst.loc |
Windows Windows.X64 Windows.IA64 | HKEY_LOCAL_MACHINE/Software/Oracle/inst.loc |
oraInst.loc
file:-invPtrLoc
flag to specify another inventory pointer file. The syntax is as follows:oraInst.loc
file is empty, Oracle Universal Installer prompts you to create a new inventory.inventory.xml
file:$ORACLE_HOME/cfgtoollogs
directory.The installation logs for an installation are identified by the timestamp associated with the log files. These files are generally saved in the following format:attachHome
operation performed on 17th, May, 2009 at 6.45AM. The associated log file would be created as follows:Oracle Clusterware
flag for the Oracle home. In a shared Oracle home, the local node information is not present. This file also contains the following information:oraclehomeproperties.xml
overrides the information in inventory.xml
. This file is located here:Platform | ARU_ID |
---|---|
Apple Mac OS X (PowerPC) | 421 |
HP Tru64 UNIX | 87 |
HP-UX Itanium | 197 |
HP-UX Itanium (32-bit) | 278 |
HP-UX PA-RISC (32-bit) | 2 |
HP-UX PA-RISC (64-bit) | 59 |
IBM AIX on POWER Systems (32-bit) | 319 |
IBM AIX on POWER Systems (64-bit) | 212 |
IBM i on POWER Systems | 43 |
IBM S/390-based Linux (31-bit) | 211 |
IBM z/OS on System z | 30 |
IBM: Linux on POWER Systems | 227 |
IBM: Linux on System z | 209 |
Linux Itanium | 214 |
Linux x86 | 46 |
Linux x86-64 | 226 |
Microsoft Windows (32-bit) | 912 |
Microsoft Windows Itanium (64-bit) | 208 |
Microsoft Windows x64 (64-bit) | 233 |
Sun Solaris SPARC (32-bit) | 453 |
Sun Solaris SPARC (64-bit) | 23 |
Sun Solaris x86 (32-bit) | 173 |
Sun Solaris x86-64 (64-bit) | 267 |
Folder Name | Description |
---|---|
Scripts | Contains the scripts used for the cloning operation. |
ContentsXML | Contains the details of the components and libraries installed. |
Templates | Contains the template files used for cloning. |
oneoffs | Contains the details of the one-off patches applied. |
oraInst.loc
file.-attachHome
flag of Oracle Universal Installer. The syntax is as follows:ORACLE_HOME
CLUSTER_NODES
REMOTE_NODES
LOCAL_NODE
CLUSTER_NODES
session variable, Oracle Universal Installer takes it from the $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml
file.LOCAL_NODE
session variable, Oracle Universal Installer takes it from the $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml
file. If it does not find an entry there, it takes it from the Oracle Clusterware stack. If it is not able to find it in the stack, the first node of the CLUSTER_NODES
is taken as the LOCAL_NODE
.REMOTE_NODES
variable if you want to specify the list of remote nodes. If you want to set up the Central Inventory in the local node, you need to pass the -local
flag, and the REMOTE_NODES
variable is empty. The syntax is as follows:-local
flag, it performs the action on the local node irrespective of the cluster nodes specified.LOCAL_NODE
variable, and the CLUSTER_NODES
variable is empty. The syntax is as follows:-local
flag to attach the local Oracle home. If you are using a shared Oracle home with the -local
flag, use the -cfs
flag. This ensures that the local node information is not populated inside a shared Oracle home.<central_inventory>/logs
directory. You can also view the contents of the inventory.xml
file under the <central-inventory>/ContentsXML
directory to verify if the Oracle home is registered.inventory.xml
file present in the Central Inventory. The syntax is as follows:-local
flag to detach the Oracle home from the inventory of the local node. If you are using a shared Oracle home, use the -cfs
flag. This ensures that the local node information is not populated inside a shared Oracle home.oraInst.loc
file and get the Central Inventory location (inventory_loc
parameter) from this file./var/opt/oracle
folder./etc
folder.oraInst.loc
file by executing the following command with root privileges:HKEY_LOCAL_MACHINESoftwareOracleinst_loc
HKEY_LOCAL_MACHINESoftwareOracleinst_loc
zip
, tar
, and cpio
to compress the Oracle home.DBHome
that is registered with the default Central Inventory in the /product
directory. You want to patch this database but decide to back up the database before patching.opatch lsinventory -detail
or when you click Installed Products, the Oracle home does not appear.inventory.xml
file for a given Oracle home, Inventory Collection from the Grid Control perspective would have issues. In this event, you should remove these duplicate entries manually.inventory.xml
file. Use the OUI APIs to change the inventory.opatch lsinventory -detail
or when you click Installed Products, the Oracle home appears, but the products and components within the Oracle home are not listed.detachHome.bat / detachHome.sh
: Use this script if the Oracle home is corrupted or needs to be updated.attachHome.bat / attachHome.sh
: Use this script if the Oracle home needs to be added to the inventory.-updateNodeList
flag with the Oracle Universal Installer, it retrieves the list of nodes and updates the inventory.xml
file. If the Oracle Clusterware
tag is set to TRUE
, the Oraclehomeproperties.xml
file is updated with the Oracle Clusterware home information. For shared Oracle homes, you need to use this with the -cfs
flag. The syntax is as follows:opatch lsinventory -detail
or when you click Installed Products, the Oracle home appears, but the products and components within the Oracle home are not listed.PATH
environment variable). If you need to switch the active home or need to perform batch work which requires a 'default home' to be active, you can use the Home Selector to change the Windows NT system settings.PATH
variable, making it the first directory to be scanned for executable and library files.PATH
variable.selectHome.bat
file to register the Oracle home you selected. In silent mode, you perform this outside Oracle Universal Installer. The first Oracle home is named the 'DEFAULT_HOME
' and registers itself in the Windows NT registry under the key:PATH
variable is adjusted and the BIN
directory of the $ORACLE_HOME
is added to the environment variable.DEFAULT_HOME
' name to something else. Also, it registers all Oracle settings in the 'KEY_<Home_NAME>
' sub-key of the ORACLE
key.PATH
variable is adjusted again to add the new BIN
directory of the newly installed Oracle software. The registry variables are written to a key named 'KEY_<HOME_NAME>
'.Oracle Home Directory | Contents |
---|---|
BIN | Product executable and DLLs |
LIB | DLL files |
JLIB | All JAR files |
DBS | Common message files |
PROD1 | PROD1 product files |
PROD2 | PROD2 product files |
ORACLE_BASE
specifies the BASE
of the Oracle directory structure for OFA-compliant databases. A typical ORACLE_BASE
directory structure is described in Table 2-6. When installing an OFA-compliant database using Oracle Universal Installer, ORACLE_BASE
is set to /pm/app/oracle
by default.Directory | Content |
---|---|
admin | Administrative files |
doc | online documentation |
local | Sub-tree for local Oracle software |
product | Oracle software |
/mount_point/app/oracle/product/
release_number
. Under UNIX, the Oracle home directory might contain the following subdirectories, as well as a subdirectory for each Oracle product selected.Directory | Content |
---|---|
assistants | configuration Assistants |
bin | binaries for all products |
ctx | interMedia Text cartridge |
dbs | init sid.ora , lk sid |
install | install related files |
lib | Oracle product libraries |
jlib | Java classes |
md | Spatial cartridge |
mlx | Xerox Stemmer (for interMedia Text cartridge) |
network | Net8 |
nlsrtl | NLS run-time loadable data |
ocommon | common files for all products |
odg | data gatherer |
opsm | Parallel Server Manager Components |
oracore | core libraries |
ord | data cartridges |
otrace | Oracle TRACE |
plsql | PL/SQL |
precomp | precompilers |
rdbms | server files and libraries required for the database |
slax | SLAX parser |
sqlplus | SQL*Plus |