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:

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.

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.

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:

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.

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

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

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.