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

This chapter describes how you can deinstall the entire Enterprise Manager system—single OMS environment or multi-OMS environment with additional Oracle Management Services (OMS).

In particular, this chapter covers the following:

• Prerequisites

• Deinstallation Procedure

• After You Deinstall

Prerequisites

Before you deinstall Enterprise Manager, meet the following prerequisites:

1. (For Multi-OMS Environment) Deconfigure and delete all the additional OMS instances by running the following command from each of their homes:

   $<OMS_HOME>/bin/omsca delete -OMSNAME <oms_name>

   Note:

   • Run this command on each of the additional OMS instances.

   • You are prompted to confirm your action, and furnish the AdminServer credentials and the repository database details such as the database host name, listener port, SID, and password. Once you provide the required details, the command automatically stops the OMS, Oracle WebLogic Server, and also Oracle WebTier.

   For example, if you have two additional OMS instances named EMGC_Addln_OMS2 and EMGC_Addln_OMS3, on two different hosts, then on the first additional OMS, run the following command:

   /u01/app/Oracle/Middleware/oms/bin/omsca delete -OMSNAME EMGC_Addln_OMS2
   

   Then, on the second additional OMS, run the following command:

   /u01/app/Oracle/Middleware/oms/bin/omsca delete -OMSNAME EMGC_Addln_OMS3
   

2. (For Multi-OMS Environment) Stop all the Oracle Management Agents (Management Agent), which are running on the additional OMS hosts, by running the following command from each of their homes:

   $<AGENT_HOME>/bin/emctl stop agent

   Note:

   Run this command on each of the Management Agents configured with the additional OMS instances.

   For example, if you have two additional OMS instances with a Management Agent on each of them, then on the first additional OMS host where the first Management Agent is running, run the following command:

   /u01/app/Oracle/agent/core/12.1.0.2.0/bin/emctl stop agent
   

   Then, on the second additional OMS host where the second Management Agent is running, run the following command:

   /u01/app/Oracle/agent/core/12.1.0.2.0/bin/emctl stop agent
   

3. Deconfigure and delete the first (main) OMS where the Admin Server is configured:

   $<OMS_HOME>/bin/omsca delete -full

   For example,

   /u01/app/Oracle/Middleware/oms/bin/omsca delete -full
   

   Note:

   You are prompted to confirm your action, and furnish the AdminServer credentials and the repository database details such as the database host name, listener port, SID, and password. Once you provide the required details, the command automatically stops the OMS, Oracle WebLogic Server, and also Oracle WebTier.

4. Stop the Management Agent running on the first (main) OMS, by running the following command from its home:

   $<AGENT_HOME>/bin/emctl stop agent

   For example,

   /u01/app/Oracle/agent/core/12.1.0.2.0/bin/emctl stop agent
   

5. If you want to deinstall the entire Enterprise Manager system, including Oracle Management Repository (Management Repository) that is configured in your database, then follow these steps:

   WARNING:

   Once the Management Repository is dropped, it CANNOT be retrieved. Therefore, drop the Management Repository ONLY IF you want to deinstall the entire Enterprise Manager system, that is, all your OMS instances, Management Agents, and also the Management Repository. If you want to deinstall only the OMS (or any additional OMS), then do not drop the Management Repository.

   1. Ensure that there are no SYSMAN users logged in.

   2. Drop the Enterprise Manager Cloud Control schema (SYSMAN schema) and the Metadata schema (MDS schema) from the Management Repository by running the following command from the OMS home:

      $<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <database_host> <repository_database_port> <repository_database_sid> -action dropall -dbUser <repository_database_user> -dbPassword <repository_database_password> -dbRole <repository_database_user_role> -reposName <repository_name> -mwHome <middleware_home> -mwOraHome <middleware_ora_home> -oracleHome <OMS_HOME>

      For example,

      /u01/app/Oracle/Middleware/oms/sysman/admin/emdrep/bin/RepManager example.com 1234 sid_em -action dropall -dbUser sys -dbPassword letmein -dbRole sysdba -reposName SYSMAN -mwHome /u01/app/Oracle/Middleware/ -mwOraHome /u01/app/Oracle/Middleware/ -oracleHome /u01/app/Oracle/Middleware/oms/ 
      

      Note:

      • For Microsoft Windows, invoke RepManager.bat.

      • RepManager 12c and 11.1 support -action dropall (drops SYSMAN as well as SYSMAN_MDS) and -action drop (drops only SYSMAN). However, RepManager 10.2.0.5 supports -action drop (drops only SYSMAN).

      • The action dropall might not drop all the repository objects. For learn more about this issue and the workaround to be used, see My Oracle Support note 1365820.1.

      • If you want to drop the Enterprise Manager schema completely, then use the RepManager available in the OMS home. Do not use the one in database home because it cannot remove the Enterprise Manager schema completely.

      • OMS home or $<OMS_HOME> refers to the first (main) OMS where the Admin Server is configured.

      • -mwHome and -mwOraHome refer to the middleware home where the first (main) OMS is configured. The first (main) OMS is the OMS where the Admin Server is configured.

      • -oracleHome refers to the Oracle home of the first (main) OMS where the Admin Server is configured.

   3. Manually delete the data files mgmt.dbf and mgmt_ecm_depot1.dbf from the database home.

Deinstallation Procedure

This section describes the following:

• Deinstalling in Graphical Mode

• Deinstalling in Silent Mode

Deinstalling in Graphical Mode

To deinstall Enterprise Manager—single OMS environment or multi-OMS environment with additional OMS instances—in graphical mode, follow these steps:

Note:

• Deinstall the components in the order described in this procedure. Otherwise, the installation wizard displays an error.

• For a multi-OMS environment, perform the steps outlined in this section on each of the additional OMS instances.

1. Invoke the installer from the OMS home by running the following command:

   $<OMS_HOME>/oui/bin/runInstaller -deinstall ORACLE_HOME=<absolute_path_to_oms_home> -jreLoc <path> [-removeallfiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

   For example,

   /u01/app/Oracle/Middleware/oms/oui/bin/runInstaller -deinstall ORACLE_HOME=/u01/app/Oracle/Middleware/oms/ -jreLoc /u01/app/Oracle/Middleware/jdk16 -removeallfiles -invPtrLoc /u01/oraInst.loc
   

   Note:

   • You can invoke the installer even from the directory where you downloaded the software. For example, <software_location>/.

   • The -invPtrLoc parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

   • When you run runInstaller -help, you will see the option -nowarningonremovefiles listed. This option is currently not supported and has no effect even if you use it.

2. On the Inventory screen, select the plug-in homes, and click Remove.

3. On the Inventory screen, select the sbin home, and click Remove.

4. On the Inventory screen, select the Java Development Kit (JDK) home, and click Remove.

   Note:

   Deinstall JDK only if it was installed by the installation wizard while installing the Enterprise Manager system. Otherwise, you can skip this step.

   Note:

   After deinstalling JDK, do NOT exit the installer. If you exit the installer inadvertently, then follow these steps:

   1. Manually download and install JDK 1.6 v24+ on the OMS host. If you already have this supported version, then you can reuse it.

   2. Invoke the installer again and pass the absolute path to the location where you have JDK:

      $<OMS_HOME>/oui/bin/runInstaller -deinstall -jreLoc <JDK_HOME> [-removeallfiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

5. On the Inventory screen, select the Oracle WebTier home, and click Remove.

6. On the Inventory screen, select the following, and click Remove.

   • OMS home

   • Management Agent home

   • Oracle Common directory

7. On the Inventory screen, click Close to exit the wizard.

8. Manually delete the middleware home:

   For UNIX platforms:

   rm -rf <absolute_path_to_middleware_home>

   For Microsoft Windows platforms:

   del <absolute_path_to_middleware_home>

   Note:

   If you see an error stating that the middleware home could not be deleted because of a long path, then shorten the middleware home name in one of the following ways:

   • Rename the middleware home to a short name.

     For example, change C:\Oracle\Middleware to C:\OR\MW.

   • Mount a drive to the middleware home path.

     For example, if C:\Oracle\Middleware\oms\bin is the directory that is causing an issue, then shorten the path in such a way that path length decreases to a reasonable extent (the file path limits differ from one operating system to another).

     Mount C:\Oracle\Middleware\oms to drive Z.

     • Navigate to drive Z, and deleted the files:

       prompt>Z:

       prompt>del bin

     • Navigate to the middleware home, and delete the leftover files:

       prompt:>C:

       prompt>del C:\Oracle\Middleware\

9. Deinstall the Management Agent as described in Chapter 16.

Deinstalling in Silent Mode

To deinstall Enterprise Manager—single OMS environment or multi-OMS environment with additional OMS instances—in silent mode, follow these steps:

Note:

• Deinstall the components in the order described in this procedure. Otherwise, the installation wizard displays an error.

• For a multi-OMS environment, perform the steps outlined in this section on each of the additional OMS instances.

1. Deinstall Oracle WebLogic Server 11g Release 1 (10.3.5) following the instructions outlined in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server. See the chapter that describes how you can deinstall the software.

   The Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server is available in the Oracle WebLogic Server documentation library available at:

   http://www.oracle.com/technetwork/indexes/documentation/index.html

   Note:

   Deinstall Oracle WebLogic Server 11g Release 1 (10.3.5) only if it was installed by the installation wizard while installing the Enterprise Manager system.

2. Deinstall the plug-in homes:

   $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={absolute_path_to_plug-in_home}" ORACLE_HOME=<absolute_path_to_oms_home> -jreLoc <JDK_HOME> [-removeallfiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

   For example,

   /u01/app/Oracle/Middleware/oms/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/u01/app/Oracle/Middleware/plugins/oracle.sysman.db.oms.plugin_12.1.0.2.0,/u01/app/Oracle/agent/plugins/oracle.sysman.db.discovery.plugin_12.1.0.2.0}" ORACLE_HOME=/u01/app/Oracle/Middleware/oms -jreLoc /u01/app/Oracle/Middleware/jdk16 -removeAllFiles -invPtrLoc /u01/oraInst.loc 
   

   Note:

   • You can invoke the installer even from the directory where you downloaded the software. If you do so, then do NOT pass -removeallfiles.

     For example, if you have downloaded the software to /u01/app/Oracle/Downloads, then run the following command, skipping the -removeallfiles argument.

     /u01/app/Oracle/Downloads/Disk1/runInstaller -deinstall -silent "REMOVE_HOMES={/u01/app/Oracle/Middleware/plugins/oracle.sysman.db.oms.plugin_12.1.0.2.0,/u01/app/Oracle/agent/plugins/oracle.sysman.db.discovery.plugin_12.1.0.2.0}" ORACLE_HOME=/u01/app/Oracle/Middleware/oms -jreLoc /u01/app/Oracle/Middleware/jdk16 -invPtrLoc /u01/oraInst.loc 
     

   • When you run runInstaller -help, you will see the option -nowarningonremovefiles listed. This option is currently not supported and has no effect even if you use it.

   • To deinstall multiple plug-ins, enter the plug-in homes separated by a comma.

   • The -invPtrLoc parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

3. Deinstall the sbin home:

   $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={absolute_path_to_sbin_home}" ORACLE_HOME=<absolute_path_to_oms_home> -jreLoc <JDK_HOME> [-removeAllFiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

   For example,

   /u01/app/Oracle/Middleware/oms/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/u01/app/Oracle/agent/sbin}" ORACLE_HOME=/u01/app/Oracle/Middleware/oms -jreLoc /u01/app/Oracle/Middleware/jdk16 -removeAllFiles -invPtrLoc /u01/oraInst.loc
   

4. Deinstall the Java Development Kit (JDK) home:

   $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={absolute_path_to_jdk_home}" ORACLE_HOME=<absolute_path_to_oms_home> -jreLoc <JDK_HOME> [-removeAllFiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

   For example,

   /u01/app/Oracle/Middleware/oms/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/u01/app/Oracle/Middleware/jdk16}" ORACLE_HOME=/u01/app/Oracle/Middleware/oms -jreLoc /u01/app/Oracle/Middleware/jdk16 -removeAllFiles -invPtrLoc /u01/oraInst.loc
   

   Note:

   Deinstall JDK only if it was installed by the installation wizard while installing the Enterprise Manager system. Otherwise, you can skip this step.

5. Manually download and install JDK 1.6 v24+ on the OMS host. If you already have this supported version, then you can reuse it.

   You must reinstall JDK because the installer has a dependency on it. The new JDK can be installed anywhere on the OMS host, not necessarily in the same location where it existed before. However, ensure that you pass the -jreLoc parameter (as described in the following steps) while invoking the installer to indicate the location where you have installed the JDK.

6. Deinstall the Oracle WebTier home:

   $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={absolute_path_to_web_tier}" ORACLE_HOME=<absolute_path_to_oms_home> -jreLoc <JDK_HOME> [-removeAllFiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

   For example,

   /u01/app/Oracle/Middleware/oms/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/u01/app/Oracle/Middleware/Oracle_WT}" ORACLE_HOME=/u01/app/Oracle/Middleware/oms -jreLoc /u01/app/Oracle/Middleware/jdk16 -removeAllFiles -invPtrLoc /u01/oraInst.loc
   

7. Deinstall the OMS, the Management Agent, and the Oracle Common directory:

   $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={absolute_path_to_oracle_homes_and_directories_to_be_deinstalled}" ORACLE_HOME=<absolute_path_to_oms_home> -jreLoc <JDK_HOME> [-removeAllFiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

   Note:

   The argument REMOVE_HOMES accepts more than one path separated by a comma.

   For example,

   /u01/app/Oracle/Middleware/oms/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/u01/app/Oracle/Middleware/oms,/u01/app/Oracle/agent/core/12.1.0.2.0,/u01/app/Oracle/Middleware/oracle_common}" ORACLE_HOME=/u01/app/Oracle/Middleware/oms -jreLoc /u01/app/Oracle/Middleware/jdk16 -removeAllFiles -invPtrLoc /u01/oraInst.loc
   

8. Manually delete the middleware home:

   For UNIX platforms:

   rm -rf <absolute_path_to_middleware_home>

   For Microsoft Windows platforms:

   del <absolute_path_to_middleware_home>

9. Deinstall the Management Agent as described in Chapter 16.

After You Deinstall

The Oracle homes you deinstalled are deregistered from the central inventory. However, some files might still remain in these Oracle homes. You might also see the OMS instance base directory and the Oracle home for Web Tier. You can manually delete these files and directories.

You must also manually delete the auto-start script titled S98gcstartup. To do so, navigate to the /etc/rc.d/ directory, and search for the auto-start 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.