K Deleting the Old OMS Home

This chapter describes how you can delete the old OMS home after upgrading from 12c Release 4 (12.1.0.4), 12c Release 3 (12.1.0.3), or 12c Release 2 (12.1.0.2) to 12c Release 5 (12.1.0.5). In particular, this chapter covers the following:

K.1 Deinstalling the Old OMS Home in Graphical Mode

To deinstall the old OMS home in graphical mode, follow these steps:

IMPORTANT:

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

  2. Ensure that you do NOT remove the Management Agent that is present in the old middleware home.

    For information on moving the agent base directory of this Management Agent (that is, the central agent) outside the old Oracle Middleware home, refer the My Oracle Support note 1520010.1.

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

    $<OMS_HOME>/oui/bin/runInstaller -deinstall [-removeAllFiles -invPtrLoc <absolute_path_to_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.

    Note:

    When you invoke runInstaller or setup.exe, if the Enterprise Manager Cloud Control Installation Wizard does not appear, then it is possible that you do not have read and write access to /stage, which a subdirectory in the Disk1 directory of the Enterprise Manager software.

    There is a classpath variable that the installation wizard computes for OPatch as ../stage/Components/, and when the TEMP variable is set to /tmp, the installation wizard tries to look for the opatch JAR file in the /tmp/../stage directory, which is equivalent to /stage. However, if you do not have read and write permission on /stage, then the installation wizard can hang. Under such circumstances, verify if you have read and write access to the /stage directory. If you do not have, then set the TEMP variable to a location where the install user has access to, and then relaunch the installation wizard.

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

    Caution:

    Make sure you have selected only the OMS-related plug-in homes, and not any agent-related plug-ins.

  3. 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.0.43.0 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>]

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

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

    • OMS home

    • Oracle Common directory

      Note:

      If BI publisher was installed in the prior version of Enterprise Manager, also select the BI publisher Oracle home (Oracle_BI1).

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

K.2 Deinstalling the Old OMS Home in Silent Mode

To deinstall the old OMS home in silent mode, follow these steps:

IMPORTANT:

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

  2. Ensure that you do NOT remove the Management Agent that is present in the old middleware home.

    For information on moving the agent base directory of this Management Agent (that is, the central agent) outside the old Oracle Middleware home, refer the My Oracle Support note 1520010.1.

  1. Deinstall the plug-in homes:

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

    Note:

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

      If you invoke the installer from here, then do NOT pass -removeAllFiles.

    • 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.

    For example,

    $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/home/oracle/middleware/plugins/oracle.sysman.ssa.oms.plugin_12.1.0.2.0}" ORACLE_HOME=/home/oracle/middleware/oms -removeAllFiles -invPtrLoc /home/oracle/oraInst.loc

  2. 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> [-removeAllFiles] [-invPtrLoc <absolute_path_to_oraInst.loc>]

    For example,

    $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/home/oracle/middleware/jdk16}" ORACLE_HOME=/home/oracle/middleware/oms -removeAllFiles -invPtrLoc /home/oracle/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.

  3. Manually download and install JDK 1.6.0.43.0 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.

  4. Deinstall the Oracle WebTier home:

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

    For example,

    $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/home/oracle/middleware/Oracle_WT}" -jreLoc </home/oracle/jdk> ORACLE_HOME=/home/oracle/middleware/oms -removeAllFiles -invPtrLoc /home/oracle/oraInst.loc

  5. Deinstall the OMS and the Oracle Common directory:

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

    Note:

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

    For example, in this scenario, BI Publisher had been installed and is now being deinstalled.

    $<OMS_HOME>/oui/bin/runInstaller -deinstall -silent "REMOVE_HOMES={/home/oracle/middleware/oms,/home/oracle/middleware/oracle_common,/home/oracle/middleware/Oracle_BI1}" -jreLoc </home/oracle/jdk> ORACLE_HOME=/home/oracle/middleware/oms -removeAllFiles -invPtrLoc /home/oracle/oraInst.loc