9 Removing Oracle Database Software

This chapter describes how to completely remove Oracle software and configuration files related to the specified Oracle home. It includes information about removing Oracle software using the deinstallation tool.

The deinstallation tool removes standalone Oracle Database installations, Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) from your server, as well as Oracle Real Application Clusters (Oracle RAC) and Oracle Database Client installations.

Oracle recommends that you use the deinstallation tool to remove the entire Oracle home associated with the Oracle Database, Oracle Clusterware, Oracle ASM, Oracle RAC, or Oracle Database client installation. Oracle does not support the removal of individual products or components.

Caution:

If you have a standalone database on a node in a cluster and you have multiple databases with the same global database name (GDN), then you cannot use the deinstallation tool to remove one database only.

The following sections describe the tool, and provide information about additional options to use the tool:

Caution:

You must use the deinstallation tool from the same release to remove Oracle software. Do not run the deinstallation tool from a later release to remove Oracle software from an earlier release. For example, do not run the deinstallation tool from the 12.1.0.1 installation media to remove Oracle software from an existing 11.2.0.4 Oracle home.

9.1 About the Deinstallation Tool

Starting with Oracle Database 12c Release 1 (12.1), the deinstallation tool is integrated with Oracle Universal Installer (OUI). You can perform a deinstallation by running the setup.exe command with the -deinstall and -home options from the base directory of the Oracle Database, Oracle Database Client, or Oracle Grid Infrastructure installation media.

The deinstallation tool is also available as a separate command (deinstall) in Oracle home directories after installation. It is located in ORACLE_HOME\deinstall.

The deinstallation tool uses the information you provide and the information gathered from the software home to create a response file. Alternatively, you can supply a response file generated previously by the deinstall command using the –checkonly option, or by editing the response file template.

Using Oracle Universal Installer with the deinstall option, or running the deinstallation tool from the Oracle home, stops and removes Oracle software and its components, such as database and configuration files for a specific Oracle home.

If the software in the Oracle home is not running (for example, after an unsuccessful installation), then the deinstallation tool cannot determine the configuration, and you must provide all the configuration details either interactively or in a response file.

Caution:

When you install Oracle Database, if the central inventory contains no other registered homes besides the home that you are deconfiguring and removing, then the Deinstallation tool removes the following files and directory contents in the Oracle base directory of the Oracle Database installation owner:
  • admin

  • cfgtoollogs

  • checkpoints

  • diag

  • oradata

  • flash_recovery_area

Oracle strongly recommends that you configure your installations using an Optimal Flexible Architecture (OFA) configuration, and that you reserve Oracle base and Oracle home paths for the exclusive use of Oracle software. If you have any user data in these locations in the Oracle base that is owned by the user account that owns the Oracle software, then the deinstallation tool deletes this data.

The deinstallation tool deletes Oracle Database configuration files, user data, and fast recovery area (FRA) files even if they are located outside of the Oracle base directory path.

In addition, for Oracle Grid Infrastructure installations:

  • Oracle Automatic Storage Management Cluster File System (Oracle ACFS) must be dismounted and Oracle Automatic Storage Management Dynamic Volume Manager (Oracle ADVM) must be disabled.

  • If Grid Naming Service (GNS) is in use, then the entry for the subdomain needs to be deleted from DNS by your DNS administrator.

Oracle recommends that you run the deinstallation tool as the Oracle software installation owner. The default method for running the deinstallation tool is from the deinstall directory in the Oracle home as the installation owner:

%ORACLE_HOME%\deinstall
DRIVE_LETTER:\> deinstall\deinstall.bat

The command uses the following syntax, where variable content is indicated by italics:

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

To run the deinstallation tool from the database installation media, use the setup.exe command with the -deinstall option, followed by the -home option to specify the path of the Oracle home you want to remove using the following syntax, where variable content is indicated in italics:

setup.exe -deinstall -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 of directory for saving files] [-help]
[-tmpdir complete path of temporary directory to use] 
[-logdir complete path of log directory to use] [-help]
 

Provide information about your servers as prompted or accept the defaults.

Note:

If User Account Control is enabled, then you must create a desktop shortcut to a DOS command window. Open the command window through the Run as administrator, right-click context menu, and start the deinstallation tool.

For more information about the User Account Control, see "Managing User Accounts with User Account Control".

In addition, you can run the deinstallation tool from other locations, or with a response file, or select other options to run the tool.

  • -home

    Use this flag to indicate the home path of the Oracle home to check or deinstall. To deinstall Oracle software using the deinstall command, located in the Oracle home you plan to deinstall, provide a response file in a location outside the Oracle home, and do not use the -home flag.

    If you run the deinstallation tool from the ORACLE_HOME\deinstall path, then the -home flag is not required because the tool identifies the location of the home where it is run. If you run the tool using setup.exe -deinstall from the installation media, then -home is mandatory.

  • -silent

    Use this flag to run the deinstallation tool in noninteractive mode. This option requires one of the following:

    • A working system that it can access to determine the installation and configuration information. The -silent flag does not work with failed installations.

    • A response file that contains the configuration values for the Oracle home that is being deinstalled or deconfigured.

    You can generate a response file to use or modify by running the tool with the -checkonly flag. The tool then discovers information from the Oracle home to deinstall and deconfigure. It generates the response file that you can then use with the -silent option.

    You can also modify the template file deinstall.rsp.tmpl, located in the ORACLE_HOME\deinstall\response directory.

  • -checkonly

    Use this flag to check the status of the Oracle software home configuration. Running the deinstallation tool with the -checkonly flag does not remove the Oracle configuration. The -checkonly flag generates a response file that you can then use with the deinstallation tool and -silent option.

  • -paramfile complete path of input parameter property file

    Use this flag to run the deinstallation tool with a response file in a location other than the default. When you use this flag, provide the complete path where the response file is located.

    The default location of the response file depends on the location of the deinstallation tool:

    • From the installation media or stage location: \response

    • After installation from the installed Oracle home: ORACLE_HOME\deinstall\response.

  • -params ["name1=value" "name2=value" "name3=value" . . .]

    Use this flag with a response file to override one or more values to change it in a response file you have created.

  • -o complete path of directory for saving response file

    Use this flag to provide a path other than the default location where the response file is saved. The default location is \response\deinstall.rsp.tmpl.

    The default location of the response file depends on the location of deinstallation tool:

    • From the installation media or the stage location before installation: \response

    • After installation from the installed Oracle home: ORACLE_HOME/deinstall/response.

  • -tmpdir complete path of temporary directory

    Specifies a non-default location where Oracle Deinstallation Tool writes the temporary files for the deinstallation.

  • -logdir complete path of log directory

    Specifies a non-default location where Oracle Deinstallation Tool writes the log files for the deinstallation.

  • -help

    Use the help option (-help ) to obtain additional information about the command optional flags.

9.2 Example of Running the Deinstallation Tool

If you perform a deinstallation by running the setup.exe command with the -deinstall option from the installation media, then help is displayed unless you enter a -home flag and provide a path to the home directory of the Oracle software to remove from your system.

Use the optional flag -paramfile to provide a path to a response file.

In the following example, the setup.exe command is in the path \directory_path, where directory_path is the path to the database directory on the installation media, and C:\app\oracle\product\12.1.0\dbhome_1 is the path to the Oracle home which is removed:

DRIVE_LETTER:\> cd \directory_path
DRIVE_LETTER:\> setup.exe -deinstall -home C:\app\oracle\product\12.1.0\dbhome_1 

The following example uses a response file in the software owner location C:\Documents and Settings\oracle\:

DRIVE_LETTER:\> cd \directory_path
DRIVE_LETTER:\> setup.exe -deinstall -paramfile C:\Documents and Settings\oracle\my_db_paramfile.tmpl 

9.3 Example of Running the Deinstallation Command

If you perform a deinstallation by using the deinstall command from the ORACLE_HOME\deinstall folder, then the deinstallation starts without prompting you for an ORACLE_HOME.

Use the optional flag -paramfile to provide a path to a response file.

In the following example, the deinstall command is in the path C:\app\oracle\product\12.1.0\dbhome_1\deinstall, and it uses a response file in the software owner location C:\Documents and Settings\oracle\:

DRIVE_LETTER:\> cd \app\oracle\product\12.1.0\dbhome_1\deinstall\
DRIVE_LETTER:\> deinstall.bat -paramfile %HOMEPATH%\my_db_paramfile.tmpl

For the grid infrastructure home, use the deinstallation script (deinstall.bat) in the Oracle Grid Infrastructure for a standalone server home, which in this example is C:\app\oracle\product\12.1.0\grid:

DRIVE_LETTER:\> cd \app\oracle\product\12.1.0\grid\deinstall\
DRIVE_LETTER:\> deinstall.bat -paramfile %HOMEPATH%\my_grid_paramfile.tmpl

9.4 Example of a Deinstallation Response File for an Oracle Database

You can perform a deinstallation on a standalone Oracle Database with the -paramfile option to use the values you specify in the response file. The following is an example of a response file, in which the Oracle Database binary owner is oracle, the Oracle Database home (Oracle home) is in the path C:\app\oracle\product\12.1.0\dbhome_1, the Oracle base (where other Oracle software is installed) is C:\app\oracle, the Oracle Inventory home is C:\Program Files\Oracle\Inventory, and the local node (the node where you run the deinstallation session from) is myserver:

#Copyright (c) 2005, 2009 Oracle Corporation. All rights reserved.
ORACLE_HOME=C:\app\oracle\product\12.1.0\dbhome_1
ORACLE_BASE.orcl=C:\app\oracle
FLASH_RECOVERY_LOC.orcl=C:\app\oracle\flash_recovery_area\ORCL
STORAGE_TYPE.orcl=FS
DB_TYPE.orcl=SI_DB
NETCA_LOCAL_LISTENERS=LISTENER
LOGDIR=C:\app\oracle\product\12.1.0\dbhome_1\deinstall\logs\
NODE_LIST.orcl=myserver
ObaseCleanupPtrLoc=\tmp\deinstall2012-06-12_09-14-11AM\orabase_cleanup.lst
ARCHIVE_LOG_DESTINATION_LOC.orcl=
ORACLE_BASE=C:\app\oracle
DUMP_DESTINATION_LOC.orcl=C:\app\oracle\admin\orcl
LOCAL_SID.orcl=orcl
INVENTORY_LOCATION=C:\Program Files\Oracle\Inventory
RAW_MAPPING_FILE.orcl=
SID_LIST.orcl=orcl
DB_UNIQUE_NAME_LIST=orcl
DATAFILE_LOC.orcl=C:\app\oracle\oradata\orcl, C:\app\oracle\fast_recovery_area\orcl
HOME_TYPE=SIDB
CRS_HOME=false
CREATION_MODE.orcl=y
CONFIGFILE_LOC.orcl=
ORACLE_BINARY_OK=true
DIAG_DEST.orcl=C:\app\oracle\diag\rdbms\orcl
LOCAL_NODE=myserver
local=false
SPFILE_LOC.orcl=C:\app\oracle\product\12.1.0\dbhome_1\dbs\spfileorcl.ora
inventory_loc=C:\Program Files\Oracle\Inventory
MinimumSupportedVersion=11.2.0.1.0
silent=false
DBCA_LOG.orcl=C:\app\oracle\cfgtoollogs\dbca\orcl
ORACLE_HOME=C:\app\oracle\product\12.1.0\dbhome_1
CCR_CONFIG_STATUS=CCR_DEL_HOME
EMCA_LOG.orcl=C:\app\oracle\cfgtoollogs\emca\orcl
ORACLE_HOME_VERSION_VALID=true

9.5 Example of a Deinstallation Response File for Oracle Grid Infrastructure

You can perform a deinstallation on an Oracle Grid Infrastructure for a standalone server home with the -paramfile option to use the values you specify in the response file.

The following is an example of a response file, in which the Oracle grid infrastructure binary owner is oracle, the Oracle grid infrastructure home is in the path D:\app\oracle, the Oracle base (where other Oracle software is installed) is D:\app\12.1.0\, the central Oracle inventory home (oraInventory) is C:\Program Files\Oracle\Inventory, the local node (the node where you are run the deinstallation session from) is myserver:

# Copyright (c) 2005, 2009 Oracle Corporation.  All rights reserved.
ORACLE_HOME=C:\app\oracle\product\12.1.0\grid
LOCAL_NODE=myserver
HOME_TYPE=SIHA
ASM_REDUNDANCY=EXTERNAL
ORACLE_BASE=C:\app\oracle\
ObaseCleanupPtrLoc=C:\Users\oracle\AppData\Local\Temp\deinstall2013-01-28_05-03-31AM\utl\orabase_cleanup.lst
SCAN_PORT=0
silent=false
ASM_UPGRADE=false
ORA_CRS_HOME=C:\app\oracle\product\12.1.0\grid
MinimumSupportedVersion=11.2.0.1.0
GPNPCONFIGDIR=$ORACLE_HOME
LOGDIR=C:\Users\username\logs\
ORACLE_HOME_VERSION_VALID=true
GPNPGCONFIGDIR=$ORACLE_HOME
ORACLE_OWNER=username
ISROLLING=true
CRS_STORAGE_OPTION=0
ORACLE_BINARY_OK=true
MGMT_DB=false
NETCA_LISTENERS_REGISTERED_WITH_HAS=LISTENER
ASM_AU_SIZE=1
HUB_SIZE=0
ASM_ORACLE_BASE=C:\app\oracle
ORA_DBA_GROUP=
JREDIR=C:\app\oracle\product\12.1.0\grid\jdk\jre\
USER_IGNORED_PREREQ=false
ASM_DISK_GROUPS="+DATA"
ORA_ASM_GROUP=
LANGUAGE_ID=AMERICAN_AMERICA.WE8MSWIN1252
CSS_LEASEDURATION=400
ASM_HOME=C:\app\oracle\product\12.1.0\grid
ASM_DIAGNOSTIC_DEST=C:\app\oracle\product\OB
TZ=America/Denver
WindowsRegistryCleanupList=C:\Users\oracle\AppData\Local\Temp\deinstall2013-01-28_05-03-31AM\utl\registry_cleanup.lst
REUSEDG=false
SILENT=false
local=false
INVENTORY_LOCATION=C:\Program Files\Oracle\Inventory
GNS_CONF=false
BIG_CLUSTER=false
LISTENER_USERNAME=domainname\oracle
ASM_DISKS=\\.\ORCLDISKDATA0
ORACLE_HOME=C:\app\oracle\product\12.1.0\grid
CRS_HOME=true
ASM_IN_HOME=true
CRFHOME="C:\app\oracle\product\12.1.0\grid"
ASM_DROP_DISKGROUPS=true
OLD_ACTIVE_ORACLE_HOME=
ASM_LOCAL_SID=+ASM
JLIBDIR=C:\app\oracle\product\12.1.0\grid\jlib
VNDR_CLUSTER=false
ASM_DISK_GROUP=DATA