Skip Headers
Oracle® Database Vault Installation Guide
10g Release 2 (10.2) for Linux
Part Number B25165-01
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

F Cloning a Database Vault Oracle Home

Cloning an Oracle home involves creating a copy of the Oracle home and then configuring it for a new environment. If you are performing multiple Oracle Database Vault installations, then you may want to use this method to create each Oracle home, because copying files from an existing Oracle Database Vault installation takes less time than creating a new version of them.

This appendix includes the following topics:

F.1 Cloning a Standalone Installation

The following steps discuss cloning a standalone installation of Oracle Database Vault:

  1. Install Oracle Database Vault in the source Oracle home. The source Oracle home is used as the source directory for the cloning process.


    Note:

    The oradata directory should be outside the Oracle home.

  2. Stop all processes running from the source Oracle home.


    See Also:

    "Stop Existing Oracle Processes" for more information on stopping existing Oracle processes

  3. Archive and compress the source Oracle home using root user privileges.

    cd $ORACLE_HOME
tar -cvf filename.tar *
compress filename.tar

  4. Create a target Oracle home directory on the same machine or another machine. The target Oracle home is used as the target directory for the cloning process.

  5. Copy the compressed archive file from the source Oracle home to the target Oracle home.

  6. Extract the contents of the compressed archive file in the target Oracle home directory using root user privileges.

    cd $ORACLE_HOME
uncompress filename.tar.Z
tar -xvf filename.tar

  7. Make sure that the user that runs the cloning process has permissions to modify the files under the target Oracle home. You can change ownership of the target Oracle home directory using the following command:

    chown -R username:usergroup $ORACLE_HOME

  8. Delete all .ora files in the target Oracle home.

    rm $ORACLE_HOME/network/admin/*.ora

  9. Run Oracle Universal Installer in clone mode for the target Oracle home.

    cd $ORACLE_HOME/oui/bin
./runInstaller -clone -silent ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=new_Oracle_home_name

  10. Run Net Configuration Assistant (NetCA), for the target Oracle home, to configure the listener.

    cd $ORACLE_HOME/bin
./netca

  11. Run Database Configuration Assistant (DBCA), for the target Oracle home, to create a database.

    cd $ORACLE_HOME/bin
./dbca

  12. Run Database Configuration Assistant (DBCA) again to configure the database with Oracle Label Security (OLS).

  13. Enable SYSDBA privilege for the newly created database.

    orapwd file=filename password=password force=y nosysdba=n

    See Also:

    "Enable or Disable Connections with the SYSDBA Privilege" for more information on enabling SYSDBA access

  14. Run Database Vault Configuration Assistant (DVCA) on the newly created database with the -action option switch.

    $ORACLE_HOME/bin/dvca -action option -oh oracle_home -jdbc_str jdbc_connection_string -sys_passwd SYS_password -owner_account DV_owner_account_name -owner_passwd DV_owner_account_password [-acctmgr_account DV_account_manager_account_name] [-acctmgr_passwd DV_account_manager_password][-logfile ./dvca.log] [-silent] [-nodecrypt][-lockout] [-languages{["en"],["de"],["es"],["fr"],["it"],["ja"],["ko"],["pt_BR"],["zh_CN"],["zh_TW"]}]

    See Also:

    Appendix B, "Running DVCA After Creating a Database Vault Database" for details on running DVCA with the -action option switch

F.2 Cloning an Oracle Real Application Clusters Node

This section discusses cloning an Oracle Real Application Clusters (RAC) node. It illustrates this by cloning a RAC node, node1, to two other nodes (nodeA and nodeB). nodeA and nodeB must already be members of a cluster.


Note:

RAC cloning can only be performed in silent mode

The following steps clone node1 to nodes, nodeA and nodeB:

  1. Install Oracle Database Vault on node1.

  2. Stop all processes running from the RAC database Oracle home on node1.


    See Also:

    "Stop Existing Oracle Processes" for more information on stopping existing Oracle processes

  3. Create a tar file of the Oracle home on node1 using root user privileges. Compress the archived file.

    cd $ORACLE_HOME
tar -cvf filename.tar *
compress filename.tar

  4. Create an Oracle home directory, for the RAC database, on nodeA. Repeat the step for nodeB.

  5. Copy the compressed archive file from node1 to the Oracle home directory on nodeA. Repeat the step for nodeB.

  6. Extract the contents of the compressed archive file in the Oracle home directory on nodeA. Use root user privileges. Repeat the step for nodeB.

    cd $ORACLE_HOME
uncompress filename.tar.Z
tar -xvf filename.tar

  7. Run Oracle Universal Installer in clone mode for nodeA.

    cd $ORACLE_HOME/oui/bin
./runInstaller -clone -silent ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=Oracle_home_name "CLUSTER_NODES={nodeA,nodeB}" LOCAL_NODE=nodeA -noConfig

    Note:

    • For a shared Oracle home, you also need to also pass the -cfs parameter on the command line.

    • You can omit the LOCAL_NODE parameter in the preceding example. nodeA, being the first in the list, is automatically set as the local node.

  8. Run Oracle Universal Installer in clone mode for nodeB.

    cd $ORACLE_HOME/oui/bin
./runInstaller -clone -silent ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=Oracle_home_name "CLUSTER_NODES={nodeA,nodeB}" LOCAL_NODE=nodeB -noConfig

    Note:

    For a shared Oracle home, you also need to also pass the -cfs parameter on the command line.

  9. Run the root.sh script on nodeA. Repeat the step for nodeB.

    cd $ORACLE_HOME
./root.sh

  10. Set the environment variable, ORACLE_HOME for nodeA. Also, add $ORACLE_HOME/lib to the environment variable, LD_LIBRARY_PATH.

  11. Run Net Configuration Assistant (NetCA) on nodeA to configure the listener.

    cd $ORACLE_HOME/bin
./netca

  12. Run Database Configuration Assistant (DBCA) on nodeA to create a database.

    cd $ORACLE_HOME/bin
./dbca

  13. Run Database Configuration Assistant (DBCA) again to configure the database with Oracle Label Security (OLS).

  14. Enable SYSDBA privilege on nodeA.

    orapwd file=filename password=password force=y nosysdba=n

    See Also:

    "Enable or Disable Connections with the SYSDBA Privilege" for more information on enabling SYSDBA access

  15. Run Database Vault Configuration Assistant (DVCA) on nodeA with the -action option switch.

    $ORACLE_HOME/bin/dvca -action option -oh oracle_home -jdbc_str jdbc_connection_string -sys_passwd SYS_password -owner_account DV_owner_account_name -owner_passwd DV_owner_account_password [-acctmgr_account DV_account_manager_account_name] [-acctmgr_passwd DV_account_manager_password][-logfile ./dvca.log] [-silent] [-nodecrypt][-lockout] [-languages{["en"],["de"],["es"],["fr"],["it"],["ja"],["ko"],["pt_BR"],["zh_CN"],["zh_TW"]}]

    See Also:

    Appendix B, "Running DVCA After Creating a Database Vault Database" for details on running DVCA with the -action option switch

  16. Enable SYSDBA privilege on nodeB.

    orapwd file=filename password=password force=y nosysdba=n

    See Also:

    "Enable or Disable Connections with the SYSDBA Privilege" for more information on enabling SYSDBA access

  17. Run DVCA on nodeB with the -action optionrac switch.

    $ORACLE_HOME/bin/dvca -action optionrac -oh oracle_home -jdbc_str jdbc:oracle:oci:@instance_name -sys_passwd SYS_password -nodecrypt -silent -logfile ./dvcalog.txt

    See Also:

    "Run DVCA to Set Instance Parameters and Lock Out SYSDBA Sessions (RAC Only)" for details on running DVCA with the -action optionrac switch


Note:

  • The order of nodes specified should always be the same on all machines.

  • Oracle Clusterware should be installed on the cluster nodes prior to starting the Oracle Real Application Clusters installation.

  • The nodes for Oracle Real Application Clusters installation is a subset of the nodes for Oracle Clusterware installation.

F.3 Adding an Oracle Real Application Clusters Node

The following topics illustrate adding an Oracle Real Application Clusters (RAC) node:

F.3.1 Adding an Oracle Real Application Clusters Node Using the Graphical User Interface

The following steps discuss adding an Oracle Real Application Clusters (RAC) node using the Graphical User Interface (GUI):

  1. Perform a single node cluster RAC installation on the first node (say node1). Install Oracle Database Vault on node1.

  2. Disable Database Vault on node1.


    See Also:

    Refer to Oracle Database Vault Administrator's Guide for more information on disabling and enabling Database Vault.

  3. Run the addNode.sh script.

    cd $ORACLE_HOME/oui/bin
./addNode.sh

  4. The Node Selection page is displayed. Select the node (say node2) to be added. Click Next.

  5. The Summary page is displayed. Verify the details on the Summary page. Click Install.

  6. Run root.sh on node2, when prompted.

  7. On node2, set the environment variable, ORACLE_HOME. Also, add $ORACLE_HOME/lib to the environment variable, LD_LIBRARY_PATH.

  8. Run Net Configuration Assistant (NetCA) on node2 to configure the listener.

    cd $ORACLE_HOME/bin
./netca

  9. Run Database Configuration Assistant (DBCA) on node1 to add an instance (node2).

    cd $ORACLE_HOME/bin
./dbca

  10. Enable Database Vault on node1 and node2.


    See Also:

    Refer to Oracle Database Vault Administrator's Guide for more information on enabling and disabling Database Vault.

  11. Enable SYSDBA privilege on node2.

    orapwd file=filename password=password force=y nosysdba=n

    See Also:

    "Enable or Disable Connections with the SYSDBA Privilege" for more information on enabling SYSDBA access

  12. Run DVCA on node2 with the -action optionrac switch.

    $ORACLE_HOME/bin/dvca -action optionrac -oh oracle_home -jdbc_str jdbc:oracle:oci:@instance_name -sys_passwd SYS_password -nodecrypt -silent -logfile ./dvcalog.txt

    See Also:

    "Run DVCA to Set Instance Parameters and Lock Out SYSDBA Sessions (RAC Only)" for details on running DVCA with the -action optionrac switch

F.3.2 Adding an Oracle Real Application Clusters Node Using the Silent Mode

The following steps discuss adding an Oracle Real Application Clusters (RAC) node using the silent mode:

  1. Perform a single node cluster RAC installation on the first node (say node1). Install Oracle Database Vault on node1.

  2. Disable Database Vault on node1.


    See Also:

    Refer to Oracle Database Vault Administrator's Guide for more information on disabling and enabling Database Vault.

  3. Run addNode.sh with the -silent option.

    cd $ORACLE_HOME/oui/bin
./addNode.sh -silent "CLUSTER_NEW_NODES={node2}"

  4. Run root.sh on node2, when prompted.

  5. On node2, set the environment variable, ORACLE_HOME. Also, add $ORACLE_HOME/lib to the environment variable, LD_LIBRARY_PATH.

  6. Run Net Configuration Assistant (NetCA) on node2 to configure the listener.

    cd $ORACLE_HOME/bin
./netca

  7. Run Database Configuration Assistant (DBCA) on node1 to add an instance (node2).

    cd $ORACLE_HOME/bin
./dbca

  8. Enable Database Vault on node1 and node2.


    See Also:

    Refer to Oracle Database Vault Administrator's Guide for more information on enabling and disabling Database Vault.

  9. Enable SYSDBA privilege on node2.

    orapwd file=filename password=password force=y nosysdba=n

    See Also:

    "Enable or Disable Connections with the SYSDBA Privilege" for more information on enabling SYSDBA access

  10. Run DVCA on node2 with the -action optionrac switch.

    $ORACLE_HOME/bin/dvca -action optionrac -oh oracle_home -jdbc_str jdbc:oracle:oci:@instance_name -sys_passwd SYS_password -nodecrypt -silent -logfile ./dvcalog.txt

    See Also:

    "Run DVCA to Set Instance Parameters and Lock Out SYSDBA Sessions (RAC Only)" for details on running DVCA with the -action optionrac switch

F.4 Adding an Oracle Real Application Clusters Node Through Cloning

This section discusses adding an Oracle Real Application Clusters (RAC) node by cloning another node in the same cluster. The following steps add a RAC node (node2) by cloning an existing node (node1):

  1. Install Oracle Database Vault on node1.

  2. Stop all processes running from the RAC database Oracle home on node1.


    See Also:

    "Stop Existing Oracle Processes" for more information on stopping existing Oracle processes

  3. Create a tar file of the Oracle home on node1 using root user privileges. Compress the archived file.

    cd $ORACLE_HOME
tar -cvf filename.tar *
compress filename.tar

  4. Create an Oracle home directory, for the RAC database, on node2.

  5. Copy the compressed archive file from node1 to the Oracle home directory on node2.

  6. Extract the contents of the compressed archive file in the Oracle home directory on node2. Use root user privileges.

    cd $ORACLE_HOME
uncompress filename.tar.Z
tar -xvf filename.tar

    Note:

    Steps 3 to 6 are not required for a shared Oracle home.

  7. Disable Database Vault on node1.


    See Also:

    Refer to Oracle Database Vault Administrator's Guide for more information on disabling and enabling Database Vault.

  8. Run Oracle Universal Installer in clone mode for node2.

    cd $ORACLE_HOME/oui/bin
./runInstaller -clone -silent ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=Oracle_home_name "CLUSTER_NODES={node1,node2}" LOCAL_NODE=node2 -noConfig

    Note:

    For a shared Oracle home, you also need to also pass the -cfs parameter on the command line.

  9. Run Oracle Universal Installer with the updateNodeList option on node1.

    cd $ORACLE_HOME/oui/bin
./runInstaller -updateNodeList ORACLE_HOME=$ORACLE_HOME "CLUSTER_NODES={node1,node2}"

  10. Run the root.sh script on node2.

    cd $ORACLE_HOME
./root.sh

  11. Set the environment variable, ORACLE_HOME for node2. Also, add $ORACLE_HOME/lib to the environment variable, LD_LIBRARY_PATH.

  12. Run Net Configuration Assistant (NetCA) on node2 to configure the listener.

    cd $ORACLE_HOME/bin
./netca

  13. Run Database Configuration Assistant (DBCA) on node1 to add node2.

    cd $ORACLE_HOME/bin
./dbca

  14. Enable Database Vault on node1 and node2.


    See Also:

    Refer to Oracle Database Vault Administrator's Guide for more information on enabling and disabling Database Vault.

  15. Enable SYSDBA privilege on node2.

    orapwd file=filename password=password force=y nosysdba=n

    See Also:

    "Enable or Disable Connections with the SYSDBA Privilege" for more information on enabling SYSDBA access

  16. Run DVCA on node2 with the -action optionrac switch.

    $ORACLE_HOME/bin/dvca -action optionrac -oh oracle_home -jdbc_str jdbc:oracle:oci:@instance_name -sys_passwd SYS_password -nodecrypt -silent -logfile ./dvcalog.txt

    See Also:

    "Run DVCA to Set Instance Parameters and Lock Out SYSDBA Sessions (RAC Only)" for details on running DVCA with the -action optionrac switch

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us