| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10817-01 |
|
|
View PDF |
| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10817-01 |
|
|
View PDF |
This chapter describes how to remove or deconfigure Oracle Clusterware software from your server.
This chapter contains the following topics:
See Also:
Product-specific documentation for requirements and restrictions to remove an individual productRemove installed components in the following situations:
You have successfully installed Oracle Clusterware, and you want to remove the 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.
If you have an Oracle Database installation using Oracle Restart (Oracle Grid Infrastructure for a standalone server), and you want to configure that server as a cluster member node, then complete the following tasks:
Inspect the Oracle configuration with SRVCTL 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 -d db_unique_name srvctl config service -d db_unique_name srvctl config listener -l lsnrname
Record the configuration information for the server, as you will need this information in a later step.
Change directory to Grid_home\crs\install, for example:
C:\> cd app\product\grid\crs\install
Deconfigure and deinstall the Oracle grid infrastructure installation for a standalone server (Oracle Restart) using the following command:
C:\..\install> roothas.pl -deconfig
Prepare the server for Oracle Clusterware configuration, as described in either Chapter 1, "Typical Installation for Oracle Grid Infrastructure for a Cluster" or Chapter 2, "Advanced Installation Oracle Grid Infrastructure for a Cluster Preinstallation Tasks".
Install and configure Oracle grid infrastructure for a cluster on each node in the cluster.
Add Oracle grid infrastructure for a cluster support for your Oracle databases using the configuration information you recorded in Step 1. Use the following command syntax, where db_unique_name is the unique name of the database on the node, Oracle_home is the complete path of the Oracle home for the database, and nodename is the name of the node:
srvctl add database -d db_unique_name -o Oracle_home -x nodename
For example, if your database name is mydb1, and the node name is node1, enter the following command:
srvctl add database -d mydb1 -o C:\app\oracle\product\11.2.0\ db1 -x node1
Add each service listed in Step 1 to the database, using the command srvctl add service.
Running the rootcrs.pl command with the flags -deconfig -force enables you to deconfigure Oracle Clusterware on one or more nodes without removing the installed binaries. This feature is useful if you encounter an error on one or more cluster nodes during installation, such as incorrectly configured shared storage. 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 deconfigure Oracle Clusterware:
Log in using a member of the Administrators group on a node where you encountered an error.
Change directory to Grid_home\crs\install. For example:
C:\> cd app\11.2.0\grid\crs\install
Run rootcrs.pl with the -deconfig -force flags. For example:
C:\..\install> perl rootcrs.pl -deconfig -force
Repeat on other nodes as required.
If you are deconfiguring Oracle Clusterware on all nodes in the cluster, then on the last node, enter the following command:
C:\..\install> perl rootcrs.pl -deconfig -force -lastnode
The -lastnode flag completes deconfiguration of the cluster, including the OCR and voting disks.
The deinstall command removes Oracle Clusterware and ASM from your server. The following sections describe the deinstall.bat command, and provide information about additional options to use with the command:
Example of Running the Deinstall Command for Oracle Clusterware and ASM
Example Parameter File for Deinstall of Oracle Grid Infrastructure
The Deinstallation Tool (deinstall.bat) is available in Oracle home directories after installation as %ORACLE_HOME%\deinstall\deinstall.bat. The deinstall.bat command is also available for download from Oracle TechNet (http://www.oracle.com/technology/software/products/database/index.html). You can download it with the complete Oracle Database 11g release 2 software, or as a separate archive file.
The deinstall.bat command uses the information you provide, plus information gathered from the software home to create a parameter file. You can alternatively supply a parameter file generated previously by the deinstall.bat command using the –checkonly flag and -o flag. You can also edit a response file template to create a parameter file.
The deinstall.bat command stops Oracle software, and removes Oracle software and configuration files on the operating system for a specific Oracle home. At the end of the deinstallation process you are prompted to run the rootcrs.pl script as a user that is a member of the Administrators group.
The deinstall.bat command uses the following syntax, where variable content is indicated by italics:
deinstall.bat -home complete path of Oracle home [-silent] [-checkonly] [-local] [-paramfile complete path of input parameter property file] [-params name1=value name2=value . . .] [-o complete path and name of output file] [-help | -h]
The options are:
-home
Use this flag to indicate the home path of the Oracle home that you want to check or deinstall. To deinstall Oracle software using the deinstall.bat command located in the Oracle home being removed, provide a parameter file in a location outside the Oracle home, and do not use the -home flag.
If you run deinstall from the Grid_home\deinstall path, then the -home flag is not required because the tool knows from which home it is being run. If you use the standalone version of the tool, then -home is mandatory
-silent
Use this flag to run the command in noninteractive mode. This flag requires as input a properties file that contains the configuration values for the Oracle home that is being deinstalled or deconfigured. To provide these values, you must also specify the -paramfile flag when specifying this flag.
To create a properties file and provide the required parameters, refer to the template file deinstall.rsp.tmpl, located in the response folder. Instead of using the template file, you can generate a properties file by using the -checkonly flag with the deinstall command. The generated properties file can then be used with the -silent flag.
-checkonly
Use this flag to check the status of the Oracle software home configuration. Running the command with the -checkonly flag does not remove the Oracle configuration. This flag generates a properties file that you can use with the deinstall.bat command.
When you use the -checkonly flag to generate a properties file, you are prompted to provide information about your system. You can accept the default value the tool has obtained from your Oracle installation, indicated inside brackets ([]), or you can provide different values. To accept the defaults, click Enter.
-local
When you run deinstall.bat with this flag, it deconfigures and deinstalls the Oracle software only on the local node (the node on which you run deinstall.bat). On remote nodes, it deconfigures Oracle software, but does not deinstall the Oracle software.
Note:
This flag can only be used in cluster environments.-paramfile complete path of input parameter property file
This is an optional flag. You can use this flag to run deinstall.bat with a parameter file in a location other than the default. When you use this flag, provide the complete path where the parameter file is located.
The default location of the parameter file depends on the location of the Deinstallation tool:
From the installation media or stage location: <Drive>:\staging_location\deinstall\response
From a unzipped archive file downloaded from OTN: <Drive>:\ziplocation\deinstall\response, where <Drive>:\ziplocation refers to the directory in which the downloaded archive file was extracted.
After installation, from the installed Oracle home: %ORACLE_HOME%\deinstall\response.
-params [name1=value name2=value name3=value . . .]
Use this flag with a parameter file to override one or more values in a parameter file that you have already created.
-o complete directory path and file name for output file
Use this flag to provide a path other than the default location where the properties file is saved.
The default location of the properties file depends on the location of the Deinstallation tool:
Extracted from an archive file downloaded from OTN: <Drive>:\ziplocation\response, where <Drive>:\ziplocation\ refers to directory in which the downloaded archive file was extracted.
After installation, from the installed Oracle home: %ORACLE_HOME%\deinstall\response.
-help | -h
Use the help option (-help or -h) to obtain additional information about the command option flags.
If you use the deinstall.bat command located in an Oracle home, or the deinstall.bat command downloaded from Oracle TechNet (not installed in an Oracle home), then it writes log files in the C:\Program Files\Oracle\Inventory\logs directory. If, however, you are using the deinstall.bat command to remove the last Oracle home installed on the server, then the log files are written to:
%TEMP%\OraDeinstall<timestamp>\logs if you use the deinstall.bat command located in the Oracle home
<Drive>:\ziplocation\deinstall\logs if you use the deinstall.bat command downloaded from Oracle TechNet
If you use the separately downloaded version of deinstall.bat, then when the deinstall.bat command runs, you are prompted to provide the home directory of the Oracle software that you want to remove from your system. Provide additional information as prompted.
To run the deinstall.bat command located in an Oracle Grid Infrastructure home in the path C:\app\11.2.0\grid, enter the following command while logged in as a member of the Administrators group:
C:\> app\11.2.0\grid\deinstall\deinstall.bat
If you want to run the deinstall.bat command located in an Oracle Grid Infrastructure home and use a parameter file located at C:\users\oracle\myparamfile.tmpl, then enter the following command while logged in as a member of the Administrators group:
Grid_home\deinstall\deinstall.bat -paramfile C:\users\oracle\myparamfile.tmpl
You can generate the myparamfile.tmpl file by running the deinstall.bat command with the -checkonly and -o flags before you run the command to deinstall the Oracle home, or you can use the response file template and manually edit it to create the parameter file. For example, to generate a parameter file using the -checkonly flag, enter a command similar to the following:
Grid_home\deinstall\deinstall -checkonly -o C:\users\oracle\myparamfile.tmpl
The following is an example of a parameter file for a cluster on nodes node1 and node2, in which the Oracle Grid Infrastructure for a cluster is installed by the user oracle, the Oracle Grid Infrastructure home (Grid home) is in the path C:\app\11.2.0\grid, the Oracle base (where other Oracle software is installed) is C:\app\oracle\, the central Oracle Inventory home is C:\Program Files\Oracle\Inventory, the virtual IP addresses (VIP) are 192.0.2.2 and 192.0.2.4, the local node (the node where you are running the deinstallation session from) is node1:
#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\11.2.0\grid ASM_HOME=C:\app\11.2.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\11.2.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\11.2.0\grid JREDIR=C:\app\11.2.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= NEW_NODEVIPS="node1-vip/255.255.252.0","node2-vip/255.255.252.0" HOST_NAME_LIST=node1,node2 SCAN_NAME=myrac-scan VIP1_MASK=255.255.252.0 INVENTORY_LOCATION=C:\Program Files\Oracle\Inventory
|
 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|