9 How to Modify or Deinstall Oracle Grid Infrastructure

9.1 Deciding When to Deinstall Oracle Clusterware

There are certain situations in which you might be required to removed Oracle software.

Remove installed components in the following situations:

• You have successfully installed Oracle Clusterware, and you want to remove the Oracle Clusterware installation, either in an educational environment, or a test environment.

• You have encountered errors during or after installing or upgrading Oracle Clusterware, and you want to reattempt an installation.

• Your installation or upgrade stopped because of a hardware or operating system failure.

• You are advised by Oracle Support to reinstall Oracle Clusterware.

9.2 Migrating Standalone Grid Infrastructure Servers to a Cluster

If you have an Oracle Database installation using Oracle Restart (an Oracle Grid Infrastructure installation for a standalone server), you can reconfigure that server as a cluster member node.

1. Inspect the Oracle Restart configuration with the Server Control (SRVCTL) utility using the following syntax, where db_unique_name is the unique name for the database, and lsnrname is the name of the listener for the database:

   srvctl config database -db db_unique_name
   srvctl config service -db db_unique_name
   srvctl config listener -listener lsnrname
   

   Write down the configuration information for the server; you will need this information in a later step.

2. Stop all of the databases, services, and listeners that you discovered in step 1.

3. If present, unmount all Oracle Automatic Storage Management Cluster File System (Oracle ACFS) file systems.

4. Go to the directory Grid_home\crs\install, where Grid_home is the location of your Oracle Grid Infrastructure home (Grid home) directory, for example:

   C:\> cd app\12.1.0\grid\crs\install
   

5. Deconfigure and deinstall the Oracle Grid Infrastructure installation for a standalone server (Oracle Restart) using the following command:

   C:\..\install> roothas.bat -deconfig -force
   

6. Prepare the server for Oracle Clusterware configuration, as described in the previous chapters (Chapter 2 through Chapter 6). In addition, choose to install Oracle Grid Infrastructure for a cluster in the same location as Oracle Restart or in a different location:

   Installing in the Same Location as Oracle Restart

   1. Use the deinstallation tool to remove the Oracle Restart software, but with all disk groups intact.

   2. Proceed to step 7.

   Installing in a Different Location than Oracle Restart

   1. Install Oracle Grid Infrastructure for a cluster in the new Grid home software location

7. As the Oracle Installation user for Oracle Grid Infrastructure, run Oracle Clusterware Configuration Wizard, and save and stage the response file. For the -responseFile parameter, specify the full path name where the response file should be written by the Oracle Clusterware Configuration Wizard, for example:

   C:\> cd Grid_home\crs\config
   C:\..\config> config.bat -silent -responseFile C:\Users\dba1\scripts\GI.rsp
   

8. Mount the Oracle ASM disk group used by Oracle Restart.

9. If you used Oracle ACFS with Oracle Restart, then:

   1. Start Oracle ASM Configuration Assistant (ASMCA). Run the volenable command to enable all Oracle Restart disk group volumes.

   2. Mount all Oracle ACFS file systems manually.

10. Add back Oracle Clusterware services to the Oracle Clusterware home, using the information you wrote down in step 1, including adding back Oracle ACFS resources, by performing the following tasks:

    1. Register the Oracle ACFS resources using a command similar to the following, where Grid_home is the location of your Oracle Grid Infrastructure installation:

       C:\> Grid_home\bin\srvctl add filesystem -device \\.\ORCLDATADISK4
       -diskgroup ORestartData -volume db1 
       -mountpointpath C:\app\12.1.0\grid\db1 -user grid
       

    2. Add the Oracle Database for support by Oracle Grid Infrastructure for a cluster. Use the following command syntax, where db_unique_name is the unique name of the database on the node, and nodename is the name of the node:

       srvctl add database -db db_unique_name -oraclehome %ORACLE_HOME% -node
        nodename
       

       For example, for the database name mydb on the local node node1, first verify that the ORACLE_HOME environment variable is set to the location of the database home directory, then enter the following command to register the database with Oracle Clusterware:

       srvctl add database -db mydb -oraclehome %ORACLE_HOME% -node node1
       

    3. Register each database service, using the command srvctl add service. For example, if your database name is mydb and you created a service named myservice for this database, then enter the following command:

       srvctl add service -db mydb -service myservice
       

9.3 Changing the Oracle Grid Infrastructure Home Path

You must reconfigure Oracle Clusterware and Oracle ASM every time you move the Grid home.

1. Login as an Administrator user or the Oracle Installation user for Oracle Grid Infrastructure (for example, grid).

2. Change directory to Grid_home\bin and enter the command crsctl stop crs. For example:

   C:\> cd app\12.1.0\grid\BIN
   C:\..\BIN> crsctl stop crs
   

3. Detach the existing Grid home.

   Run a command similar to the following, where C:\app\12.1.0\grid is the existing Grid home location:

   C:\> cd app\12.1.0\grid\oui\bin
   C:\..\bin> setup.exe -silent -detachHome ORACLE_HOME=
     'C:\app\12.1.0\grid' -local
   

4. Move the installed files for Oracle Grid Infrastructure from the old Grid home to the new Grid home.

   For example, if the old Grid home is C:\app\12.1.0\grid and the new Grid home is D:\app\12c\grid, use the following command:

   C:\> xcopy C:\app\12.1.0\grid D:\app\12c\grid /E /I /H /K
   

5. Clone the Oracle Grid Infrastructure installation, using the instructions provided in "Creating a Cluster by Cloning Oracle Clusterware Step 3: Run the clone.pl Script on Each Destination Node," in Oracle Clusterware Administration and Deployment Guide.

   When you navigate to the Grid home\clone\bin directory and run the clone.pl script, provide values for the input parameters that provide the path information for the new Grid home.

   Note:

   You cannot specify a different Oracle Home user when changing the Oracle Grid Infrastructure home path.

6. Enter the following command to start Oracle Clusterware in the new home location:

   D:\> cd app\12c\grid\crs\install
   D:\..install\> rootcrs.bat -patch -dstcrshome D:\app\12c\grid
   

7. Repeat steps 1 through 4 on each cluster member node.

9.4 Unconfiguring Oracle Clusterware Without Removing the Software

By running rootcrs.pl -deconfig -force on nodes where you encounter an installation error, you can deconfigure Oracle Clusterware on those nodes, correct the cause of the error, and then run rootcrs.pl again to reconfigure Oracle Clusterware.

Running the rootcrs.bat command with the flags -deconfig -force enables you to deconfigure Oracle Clusterware on one or more nodes without removing the installed software. This feature is useful if you encounter an error on one or more cluster nodes during installation, such as incorrectly configured shared storage.

Before deconfiguring Oracle Clusterware you must:

• Stop any databases, services, and listeners that may be installed and running

• Dismount ACFS file systems

• Disable ADVM volumes

1. Log in using a member of the Administrators group on a node where you encountered an error during installation.

2. Stop any databases, services, and listeners currently running from the Grid home.

3. If present, unmount all Oracle Automatic Storage Management Cluster File System (Oracle ACFS) file systems.

4. Change directory to Grid_home\crs\install. For example:

   C:\> cd C:\app\12.1.0\grid\crs\install
   

5. Run rootcrs.bat with the -deconfig -force flags. For example:

   C:\..\install> rootcrs.bat -deconfig -force
   

   Note:

   The -force flag must be specified when running the rootcrs.bat script if there exist running resources that depend on the resources started from the Oracle Clusterware home you are deleting, such as databases, services, or listeners. You must also use the -force flag if you are removing a partial, or failed installation.

6. Repeat Step 1 through Step 5 on other nodes as required.

7. If you are deconfiguring Oracle Clusterware on all nodes in the cluster, then on the last node, enter the following command:

   C:\..\install> rootcrs.bat -deconfig -force -lastnode
   

   The -lastnode flag completes deconfiguration of the cluster, including the Oracle Cluster Registry (OCR) and voting files.

9.5 Removing Oracle Clusterware and Oracle ASM Software

The deinstall tool removes Oracle Clusterware and Oracle ASM from your server.

• About the Deinstallation Tool

• Using the Deinstallation Tool to Remove Oracle Clusterware and Oracle ASM

• Example Response File for Deinstall of Oracle Grid Infrastructure

deinstall.bat [-silent] [-checkonly] [-local] 
[-paramfile complete path of input response file] 
[-params name1=value name2=value . . .] 
[-o complete path of directory for saving files] 
[ -tmpdir complete path of temporary directory to use] [ -logdir complete path of log directory to use] [-help]
 

setup.exe -deinstall -home complete path of Oracle home [-silent] [-checkonly] 
[-local] [-paramfile complete path of input response file] 
[-params name1=value[ name2=value ...]] 
[-o complete path of directory for saving files] 
[ -tmpdir complete path of temporary directory to use] [ -logdir complete path of log directory to use] [-help]
 

C:\> app\12.1.0\grid\deinstall\deinstall.bat

C:\> cd directory_path
C:\..database> setup.exe -deinstall -home C:\app\12.1.0\grid

C:\> cd %ORACLE_HOME%
C:\..grid> deinstall\deinstall.bat -paramfile D:\Users\oracle\paramfile4.tmpl

C:\> app\12.1.0\grid\deinstall\deinstall.bat -checkonly -o C:\Users\oracle\

#Copyright (c) 2005, 2009 Oracle Corporation.  All rights reserved.
VIP1_IP=192.0.2.2
LOCAL_NODE=node1
ORA_VD_DISKGROUPS=+DATA
VIP1_IF=PublicNIC
OCRID=
ObaseCleanupPtrLoc=C:\Temp\OraDeinstall112010-02-11_10-14-30AM\utl\...
HELPJAR_NAME=help4.jar
local=false
ORACLE_HOME=C:\app\12.1.0\grid
ASM_HOME=C:\app\12.1.0\grid
ASM_DISK_GROUPS=
ASM_DISK_GROUP=DATA
ORA_DBA_GROUP=
ASM_DISCOVERY_STRING=
NEW_HOST_NAME_LIST=
PRIVATE_NAME_LIST=
ASM_DISKS=\\.\ORCLDISKDATA0,\\.\ORCLDISKDATA1,\\.\ORCLDISKDATA2
ASM_DISKSTRING=
CRS_HOME=true
JLIBDIR=C:\app\12.1.0\grid\jlib
OCRLOC=
JEWTJAR_NAME=jewt4.jar
EMBASEJAR_NAME=oemlt.jar
CRS_STORAGE_OPTION=1
ASM_REDUNDANCY=EXTERNAL
GPNPGCONFIGDIR=$ORACLE_HOME
LANGUAGE_ID='AMERICAN_AMERICA.WE8MSWIN1252'
CRS_NODEVIPS='node1-vip/255.255.252.0/PublicNIC,node2-vip/255.255.252.0/PublicNIC'
ORACLE_OWNER=Administrator
OLD_ACTIVE_ORACLE_HOME=
GNS_ALLOW_NET_LIST=
silent=false
LOGDIR=C:\Temp\OraDeinstall112010-02-11_10-14-30AM\logs\
OCFS_CONFIG=
NODE_NAME_LIST=node1,node2
GNS_DENY_ITF_LIST=
ORA_CRS_HOME=C:\app\12.1.0\grid
JREDIR=C:\app\12.1.0\grid\jdk\jre
ASM_LOCAL_SID=+asm1
ORACLE_BASE=C:\app\oracle\
GNS_CONF=false
NETCFGJAR_NAME=netcfg.jar
ORACLE_BINARY_OK=true
OCR_LOCATIONS=NO_VAL
ASM_ORACLE_BASE=C:\app\oracle
OLRLOC=
GPNPCONFIGDIR=$ORACLE_HOME
ORA_ASM_GROUP=
GNS_DENY_NET_LIST=
OLD_CRS_HOME=
EWTJAR_NAME=ewt3.jar
NEW_NODE_NAME_LIST=
GNS_DOMAIN_LIST=
ASM_UPGRADE=false
NETCA_LISTENERS_REGISTERED_WITH_CRS=LISTENER
CLUSTER_NODES=node1,node2
CLUSTER_GUID=
NEW_PRIVATE_NAME_LIST=
ASM_DIAGNOSTIC_DEST=C:\APP\ORACLE
CLSCFG_MISSCOUNT=
SCAN_PORT=1521
ASM_DROP_DISKGROUPS=true
NETWORKS="PublicNIC"/192.0.2.1:public,"PrivateNIC"/10.0.0.1:cluster_interconnect
OCR_VOTINGDISK_IN_ASM=true
NODELIST=node1,node2
ASM_IN_HOME=true
HOME_TYPE=CRS
GNS_ADDR_LIST=
CLUSTER_NAME=myrac-cluster
SHAREJAR_NAME=share.jar
VOTING_DISKS=NO_VAL
SILENT=false
VNDR_CLUSTER=false
GPNP_PA=
CSS_LEASEDURATION=400
REMOTE_NODES=node2
ASM_SPFILE=
HOST_NAME_LIST=node1,node2
SCAN_NAME=myrac-scan
VIP1_MASK=255.255.252.0
INVENTORY_LOCATION=C:\Program Files\Oracle\Inventory