Skip Headers
Oracle® Audit Vault Collection Agent Installation Guide
Release 10.3

Part Number E23588-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Removing Oracle Audit Vault Collection Agent Software

This chapter describes the process of removing Oracle Audit Vault collection agent software. It contains the following topics:

4.1 Stopping the Oracle Audit Vault Collection Agent Software

Use the following procedure to uninstall the Oracle Audit Vault collection agent software:

  1. Use the Oracle Audit Vault Control (AVCTL) commands documented in Oracle Audit Vault Administrator's Guide to:

    1. Stop all collectors (avctl stop_collector) running on the collection agent

    2. Stop the collection agent itself (avctl stop_agent).

  2. Continue to Section 4.2.1.

4.2 Removing Oracle Audit Vault Collection Agent Software Using the Deinstallation Tool

The deinstall command removes Oracle Audit Vault Collection Agent installation.

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

4.2.1 About the Deinstallation Tool

The Deinstallation Tool (deinstall) is available in the installation media before installation, and is available in Oracle home directories after installation. It is located in the $ORACLE_HOME/deinstall directory.

The deinstall 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 command using the –checkonly option, or by editing the response file template.

Caution:

When you run the deinstall command, if the central inventory (oraInventory) contains no other registered homes besides the home that you are deconfiguring and removing, then the deinstall command 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 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 deinstall command deletes this data.

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

deinstall -home complete path of Oracle home [-silent] [-checkonly] [-local]
[-cleanupObase] [-paramfile complete path of input parameter property file] [-params name1=value
name2=value . . .] [-o complete path of directory for saving files] [-help]
 

The default method for running the deinstall tool is from the deinstall directory in the Oracle home as the installation owner:

$ $ORACLE_HOME/deinstall/deinstall

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

The deinstall command stops Oracle software, and removes Oracle software and configuration files on the operating system.

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

The options are:

  • -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 in the Oracle home you plan to deinstall, provide a parameter file in another location, and do not use the -home flag.

    If you run deinstall from the $ORACLE_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 silent or response file mode. If you use the -silent flag, then you must use the -paramfile flag, and provide a parameter file that contains the configuration values for the Oracle home to deinstall or deconfigure.

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

    You can also modify the template file deinstall.rsp.tmpl, located in the response folder.

  • -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. The -checkonly flag generates a parameter file that you can use with the deinstall command.

  • -local

    Use this flag on a multinode environment to deinstall Oracle software in a cluster.

    When you run deinstall with this flag, it deconfigures and deinstalls the Oracle software on the local node (the node where deinstall is run). On remote nodes, it deconfigures Oracle software, but does not deinstall the Oracle software.

  • -cleanupOBase

    Use this flag to force the removal of all the contents in the Oracle base directory, including the admin, oradata, and flash_recovery_area directories. This flag forces an Oracle base removal only if the Oracle home that you specify with the -home flag is the only Oracle home associated with the Oracle base directory. This flag is available with the deconfig tool available in the Oracle Grid Infrastructure and Oracle Database 11.2.0.3 patch release, and from Oracle Technology Network (OTN).

  • -paramfile complete path of input parameter property file

    Use this flag to run deinstall 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 deinstall:

    • From the installation media or stage location: $ORACLE_HOME/inventory/response.

    • From a unzipped archive file from OTN: /ziplocation/response.

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

  • -params [name1=value name 2=value name3=value . . .]

    Use this flag with a parameter file to override one or more values that you want to change in a parameter file you have already created.

  • -o complete path of directory for saving response files

    Use this flag to provide a path other than the default location where the properties file (deinstall.rsp.tmpl) is saved.

    The default location of the parameter file depends on the location of deinstall:

    • From the installation media or stage location before installation: $ORACLE_HOME/

    • From a unzipped archive file from OTN: /ziplocation/response/.

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

  • -help

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

4.2.2 Example of Running the Deinstall Command

As the deinstall command runs, you are prompted to provide the home directory of the Oracle software to remove from your system. Provide additional information as prompted.

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

In the following example, the deinstall command is in the path /u01/app/oracle/product/10.3.0/client_1/deinstall, and it uses a parameter file in the software owner location /home/usr/oracle:

# cd /u01/app/oracle/product/10.3.0/client_1/deinstall/
# ./deinstall -paramfile /home/usr/oracle/myparamfile.tmpl

If you enter the deinstall command outside of the $ORACLE_HOME/deinstall folder, then help is displayed, unless you enter a -home flag and provide a path. If you run the deinstall command from the $ORACLE_HOME/deinstall folder, then deinstallation starts without prompting you for a home address.

4.2.3 Example of a Deinstallation Parameter File

You can run the deinstall command with the -paramfile option to use the values you specify in the parameter file. The following is an example of a parameter file, in which the Oracle Database binary owner is oracle, the Oracle Database home (Oracle home) is in the path /u01/app/oracle/product/10.3.0/av_agent/, the Oracle base (where other Oracle software is installed) is /u01/app/oracle/, the central Oracle Inventory home (oraInventory) is /u01/app/oraInventory, and the client is client1:

ORACLE_BASE=/u01/app/oracle
INVENTORY_LOCATION=/u01/app/oraInventory
CRS_HOME=false
HOME_TYPE=CLIENT
silent=false
local=false
LOCAL_NODE=node1
ObaseCleanupPtrLoc=/var/tmp/install/orabase_cleanup.lst.
LOGDIR=/u01/app/oraInventory/logs/
ORACLE_HOME=/u01/app/oracle/product/10.3.0/av_agent

4.3 For Microsoft Windows Systems: Manually Remove the Remaining Oracle Audit Vault Collection Agent Components

Oracle Universal Installer does not remove all Oracle Audit Vault collection agent components. After using Oracle Universal Installer to remove Oracle Audit Vault collection agent components, you must manually remove the remaining registry keys, environment variables, Start menu options, and directories.

This section contains these topics:

Note:

In rare situations, you might want to correct serious system problems by completely removing Oracle Audit Vault collection agent components manually from the computer without first deinstalling Oracle Audit Vault collection agent with Oracle Universal Installer. Do this only as a last resort, and only if you want to remove all Oracle Audit Vault collection agent components from your system.

4.3.1 Removing Oracle Audit Vault Collection Agent Keys from the Registry Editor on Microsoft Windows

Oracle Universal Installer does not delete all services created by Oracle Net Configuration Assistant. In addition, it does not delete several other registry keys. You must remove any existing registry keys manually by following the instructions in one of the following sections:

Caution:

Use Microsoft Registry Editor at your own risk. Incorrectly using the Registry Editor can cause serious problems and might require you to reinstall your operating system.

4.3.1.1 Removing Only the Oracle Audit Vault Collection Agent Service Registry Key

To remove only the Oracle Audit Vault collection agent Service registry entry (if it exists):

  1. Log in as a member of the Administrators group.

  2. Ensure that you first follow the instructions in Step 3 in Section 4.1 about stopping Oracle services on Microsoft Windows before removing Oracle Audit Vault collection agent components.

  3. From the Start menu, choose Run, and then enter the following command:

    regedit
    
  4. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete the Oracle Audit Vault Agent - agent name registry entry.

    When you ran Oracle Universal Installer to deinstall Oracle Audit Vault collection agent, it deleted all other Oracle Net services.

  5. Exit the Registry Editor.

  6. Restart your computer.

4.3.1.2 Removing Only the Oracle Audit Vault Collection Agent Registry Keys

To remove the Oracle Audit Vault collection agent registry keys from a computer (if any exist):

Caution:

These instructions remove only the Oracle Audit Vault collection agent components, services, and registry entries from your computer. Exercise extreme care when removing registry entries. Removing incorrect entries can break your system. Any database files under ORACLE_BASE\ORACLE_HOME\Oracle Audit Vault Agent Name should be deleted only after completing these instructions.
  1. Log in as a member of the Administrators group.

  2. Ensure that you first follow the instructions in Step 3 in Section 4.1 about stopping Oracle Audit Vault collection agent Microsoft Windows service before removing the Oracle Audit Vault collection agent components.

  3. From the Start menu, choose Run, and enter the following command:

    regedit
    
  4. Go to HKEY_LOCAL_MACHINE\SOFTWARE.

  5. Delete the ORACLE key named KEY_AgentHOME_NAME, similar to KEY_OraAV10g_home1.

  6. Exit the Registry Editor.

  7. Restart your computer.

4.3.2 Updating the PATH Environment Variable Path

Check the PATH environment variable and remove any Oracle entries.

  1. Display System in the Control Panel.

  2. Select the Advanced tab and then click Environment Variables.

  3. Select the system variable PATH and edit it to remove any Oracle entries.

    For example, remove Oracle entries that contain ORACLE_BASE\ORACLE_HOME in the Path variable. You may see a Path variable that contains entries similar to the following:

    ORACLE_BASE\ORACLE_HOME\product\10.3.0\av_agent_1\bin
    
  4. Save any changes and exit System.

4.3.3 Removing Oracle Audit Vault Collection Agent from the Start Menu

Check the Start menu for any Oracle Audit Vault collection agent entries and remove them.

Follow these steps:

  1. Select Start, then Programs, then Oracle - Agent HOME_NAME.

  2. Right-click Oracle - Agent HOME_NAME, and from the menu, select Delete.

You can also remove Oracle Audit Vault collection agent menu entries by using the following method:

  1. Right-click the Start button to display the shortcut menu.

  2. Select the Explore All Users option.

  3. Under Documents and Settings, expand the \Start Menu\Programs folder.

  4. Right-click and delete the Oracle - Agent HOME_NAME folder.

4.3.4 Removing Oracle Audit Vault Collection Agent Directories

After removing all Oracle Audit Vault collection agent registry keys and restarting the computer, delete any existing Oracle Audit Vault collection agent directories and files.

  1. Using My Computer or Microsoft Windows Explorer, delete the SYSTEM_DRIVE:\program files\oracle directory.

  2. Using My Computer or Microsoft Windows Explorer, delete the Oracle Audit Vault ORACLE_BASE directory on your hard drive.