Deinstalling Enterprise Manager (Single and Multi-OMS Environments)

25 Deinstalling Enterprise Manager (Single and Multi-OMS Environments)

This chapter describes how you can deinstall an entire Enterprise Manager system, and also how you can remove the entries of an Oracle Management Service (OMS) from the Oracle Management Repository (Management Repository) in case you lost the host where the OMS was running.

In particular, this chapter covers the following:

Deinstallation Scope

The following describes the scope of deinstalling the components of an Enterprise Manager system.

Table 25-1 Deinstallation Scope

Environment Type	OMS Type	Installation Type	Components Deinstalled	Components Not Deinstalled
Single OMS, Multi-OMS	First OMS	Fresh Installation	First OMS (including the instance home) Central Agent Management Repository	Not Applicable
Single OMS, Multi-OMS	First OMS	Upgrade	First OMS (including the instance home) Management Repository	Central Agent. To deinstall the central agent, see Deinstalling Oracle Management Agents.
Multi-OMS	Additional OMS	Fresh Installation	Additional OMS	Management Repository Standalone Management Agent running on the additional OMS host. To deinstall the central agent, see Deinstalling Oracle Management Agents.
Multi-OMS	Additional OMS	Upgrade	Additional OMS	Management Repository Standalone Management Agent running on the additional OMS host. To deinstall the central agent, see Deinstalling Oracle Management Agents.

Deinstalling the Enterprise Manager System

To deinstall an Enterprise Manager system in a single OMS environment or multi-OMS environment, follow these steps:

Note:

Before you begin, understand the scope of deinstallation as described in Deinstallation Scope.
For a multi-OMS environment, first deinstall the additional OMS instances, and then deinstall the first OMS.
The steps outlined in this section not only deinstall the OMS instances but also deinstall the Management Repository.
Once the Management Repository is deinstalled from the database, you can reuse the empty database for any other purpose. Only the Enterprise Manager schema is removed from the database, but the physical files or the software binaries of the database software will continue to remain on the host.
The steps outlined in this section do not deinstall, remove, or roll back any of the patches applied on the database.
For a fresh OMS installation, either the first OMS or an additional OMS, the steps outlined in this section automatically remove the middleware, the OMS, the OMS instance home, and the Management Agent directories, but not the contents of the shared location configured for Oracle BI Publisher. You must manually remove its contents.
For an upgraded OMS, either the first OMS or an additional OMS, the steps outlined in this section automatically remove the middleware, the OMS, and the OMS instance home directories, but not the Management Agent directory and the contents of the shared location configured for Oracle BI Publisher. You must deinstall the Management Agent as described in Deinstalling Oracle Management Agents, and manually remove the contents of the shared location configured for Oracle BI Publisher.

Copy the deinstallation script from the Oracle home of the OMS host to a temporary or stage location.

cp <ORACLE_HOME>/sysman/install/EMDeinstall.pl <temporary_location>

For example,

cp /u01/software/em13c/oraclehome/sysman/install/EMDeinstall.pl /u01/tmp_deinstall
Deinstall the OMS.

<ORACLE_HOME>/perl/bin/perl <temporary_location>/EMDeinstall.pl -mwHome <ORACLE_HOME> -stageLoc <temporary_location>

You will be prompted for database credentials (SYS and SYSMAN) and the WebLogic Domain credentials. Enter the credentials and proceed with the deinstallation.

For example,

/u01/software/em13c/oraclehome/perl/bin/perl /u01/tmp_deinstall/EMDeinstall.pl -mwHome /u01/software/em13c/oraclehome -stageLoc /u01/tmp_deinstall

Note:

The deinstallation process removes the entry of the S98gcstartup script, an auto-start script, from the /etc/oragchomelist file, but does not remove the script itself. You can leave this script and the symlinks associated with it because when you install Enterprise Manager again on the same host, the installer automatically overwrites the script and re-create the symlinks.

However, if you want to clear the host of any Oracle products, then Oracle recommends that you manually delete this script and the symlinks associated with it. To do so, navigate to the /etc/rc.d/ directory, and search for the script S98gcstartup. This script is usually present in a subdirectory within the /etc/rc.d/ directory. Navigate to the subdirectory where the script is found and delete the script. For example, /etc/rc.d/rc3.d/S98gcstartup or /etc/rc.d/init.d/gcstartup/S98gcstartup.

Deinstalling or Undeploying Only Plug-ins from the OMS

If you want to deinstall or undeploy only the plug-ins from the OMS, and not the entire Enterprise Manager system, then use the Plug-ins page within the Enterprise Manager Cloud Control Console. For instructions, see the Oracle Enterprise Manager Cloud Control Administrator's Guide. Do NOT use this chapter to undeploy only the plug-ins.

Deleting OMS Entries from the Management Repository

If you lose the host where an additional OMS is running, then make sure you manually delete the entry for that OMS from the Management Repository. To do so, follow these steps:

Run the following command to deconfigure Oracle WebLogic Server, applications, and so on from the WebLogic Domain; remove all OMS-related entries from the Management Repository; and delete these targets of the OMS: oracle_oms, oracle_oms_pbs, oracle_oms_console.

$ORACLE_HOME/bin/omsca delete
Manually delete the following WebLogic targets of the OMS.
- /EMGC_GCDomain/GCDomain/EMGC_OMS2 (weblogic_j2eeserver)
- /EMGC_GCDomain/instance2/ohs2 (oracle_apache)

Now Enterprise Manager will not have any reference of the deleted additional OMS. If you want to delete the OMS, follow the instructions outlined in Deinstalling the Enterprise Manager System.