1. Installation and Configuration Guide for Exadata Database Machine
  2. OEDA Command Line Interface
  3. OEDACLI Command Reference
  4. DATABASEHOME
  5. ADD DATABASEHOME

4.3.9.1 ADD DATABASEHOME

This command adds an Oracle database home to an existing cluster.

Syntax

ADD DATABASEHOME 
   OWNER=owner 
   DBVERSION=version
   DBHOMELOC=database_home_path 
   [ DBHOMENAME=database_home_name ] 
   [ INVLOC=inventory_location ] 
   [ DBLANG=database_language ]
   [ MACHINELIST='machine_list' ] 
   [ PATCHLIST='patch_list' ]
   [ BASEDIR=base_directory ] 
   [ VOLUMESIZE=volume_size ]
   [ INSTALLTYPE={ CLONE | ZIP } ]
WHERE
   { CLUSTERNUMBER=cluster_number | 
     CLUSTERNAME=cluster_name |
     CLUSTERID=cluster_id }

Arguments

You can specify the following attributes for the new Oracle database home:

  • OWNER : (Mandatory) Specifies the operating system user that owns the Oracle home.

  • DBVERSION : (Mandatory) Specifies the version of the software in the database home, including the release update (RU), for example 12.1.0.2.170418.

  • DBHOMELOC : (Mandatory) Specifies the file system path for the new Oracle database home directory.

  • DBHOMENAME : Specifies the name of the new database home. The default value is the standard template name, for example, dbhome_1.

  • INVLOC : Specifies the location of the Oracle inventory directory. The default value is derived from the cluster home.

  • DBLANG : Specifies the language to use with the Oracle home. The default value is all_langs.

  • MACHINELIST : Specifies a list of nodes to create the Oracle home on. The default value is list of nodes registered with the Grid home.

  • PATCHLIST : Specifies a comma-separated list of patches for the database home. The default value is derived from DBVERSION.

  • BASEDIR : Specifies the location of the Oracle Base directory. The default value is derived from OWNER.

  • VOLUMESIZE : Specifies the size of the home directory volume. The default value is 50 GB. This argument is applicable only for database homes for Oracle VM clusters.

  • INSTALLTYPE: Specifies the software installation method to use. The options are:

    • CLONE: Uses image files to clone a software installation. The image files include the base software release, and may also include additional patches and updates. By including updates in the image files, this method reduces deployment time and improves deployment consistency.

      The CLONE software installation method is the only supported method for database homes in a virtual machine (VM) deployment. This option is also available for database homes in a physical (bare metal) deployment.

    • ZIP: Performs a fresh software installation by using compressed (zip) files that contain the software release. This method does not include additional patches or updates.

      This option is not available for database homes in a virtual machine (VM) deployment.

    If you do not specify the INSTALLTYPE setting, then the default setting matches the INSTALLTYPE setting in the containing cluster.

The following arguments are available in the WHERE clause:

  • CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

  • CLUSTERNAME : Specifies the name of the cluster

  • CLUSTERID : Specifies the es.xml ID of the cluster

Example 4-18 Adding a Database Home to a Deployment using OEDACLI

This example shows how to add a new Oracle home. dbversion should specify both the base version and the target release update (RU). In this example, we are setting up a new Oracle database home with 12.1.0.2.170418. The software will be installed under /u01/app/oracle/product/12.1.0.2/dbhome_2. 

./oedacli

oedacli> LOAD FILE NAME=Oracle-test12.xml
SUCCESS - file loaded OK 
Customer : ora07adm01 - Oracle

oedacli> ADD DATABASEHOME OWNER='oracle' DBVERSION='12.1.0.2.170418' DBHOMELOC='/u0
1/app/oracle/product/12.1.0.2/dbhome_2' WHERE CLUSTERNUMBER=1

oedacli> SAVE ACTION

oedacli> MERGE ACTIONS
processMerge 
processMergeActions 
Merging Action : add databasehome owner='oracle' dbversion='12.1.0.2.170418' 
dbhomeloc='/u01/app/oracle/product/12.1.0.2/dbhome_2' where clusternumber=1 
Merging ADD DATABASEHOME 
Action Validated and Merged OK

oedacli> DEPLOY ACTIONS
Deploying Action ID : 1 add databasehome owner='oracle' dbversion='12.1.0.2.170418'
 dbhomeloc='/u01/app/oracle/product/12.1.0.2/dbhome_2' where clusternumber=1 
Deploying ADD DATABASEHOME 
Checking local files.. 
Required files are: 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/p26022196_121020
_Linux-x86-64.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/p26027162_121020
_Linux-x86-64.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/p6880880_122010_
Linux-x86-64.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/linuxamd64_12102
_database_2of2.zip exists... 
SUCCESS: Required file /scratch/cpabba/Oeda/main/linux-x64/WorkDir/linuxamd64_12102
_database_1of2.zip exists... 
Copying required files... 
Checking status of remote files... 
Checking status of existing files on remote nodes... 
Getting status of local files... 
Copying file: linuxamd64_12102_database_1of2.zip to node node1adm01.example.com 
Copying file: linuxamd64_12102_database_2of2.zip to node node1adm01.example.com 
Copying file: p26022196_121020_Linux-x86-64.zip to node node1adm01.example.com 
Copying file: p26027162_121020_Linux-x86-64.zip to node node1adm01.example.com 
Copying file: p26022196_121020_Linux-x86-64.zip to node node1adm02.example.com 
Copying file: p26027162_121020_Linux-x86-64.zip to node node1adm02.example.com 
Completed copying files... 
Extracting files... 
Completed extracting files... 
Validating nodes for database readiness... 
Installing database software ... 
Running database installer on node node1adm01.example.com ... Please wait... 
After running database installer... 
Patching... 
Done... 
Done

Parent topic: DATABASEHOME