10 How to Remove or Disable an Old Oracle Home?

After in-place upgrade, you can remove or disable an old Oracle Home if you have configured the Domain home outside the old Oracle Home.

Note:

When you perform in-place upgrade, the previous Oracle Home remains. If you have configured the Domain home within the old Oracle Home, don’t remove the old Oracle Home.

Perform the following steps to remove or disable the old Oracle Home.

1. Back up the old Oracle Home.
2. Perform these steps before deleting the old Oracle Home.
   1. Stop all the services.
      • In Linux, DOMAIN_HOME/bitools/bin/stop.sh
      • In Windows, DOMAIN_HOME/bitools/bin/stop.cmd
   2. Copy the em.ear file from the applications directory of the old Oracle Home to the applications directory of the new Oracle Home.

      For example: ORACLE_HOME path/user_projects/applications/bi/em.ear

      If required, create the applications/bi folders under the new ORACLE_HOME/user_projects path. For example: New OAS ORACLE_HOME path/user_projects/applications/bi/em.ear

   3. Delete or rename the tmp folder under AdminServer.

      mv $Domain_Home/servers/AdminServer/tmp $Domain_Home/servers/AdminServer/tmp_old

   4. Modify the Domain_Home/config/config.xml file.

      The config.xml file should contain the application deployment and source location, for example:

      <app-deployment>
      <name>em</name>
      <target>AdminServer</target>
      <module-type>ear</module-type>
      <source-path>New OAS  Oracle_Home path/user_projects/applications/bi/em.ear</source-path>
      <deployment-order>400</deployment-order>
      <security-dd-model>DDOnly</security-dd-model>
      <staging-mode>nostage</staging-mode>
      </app-deployment>
      

      Note:

      Correct the source-path to point to the em.ear file from the New OAS ORACLE_HOME path.

      If the content mismatches, make sure the above content exists in the config.xml file for the 'em' deployment.

      Note:

      In case you have performed the steps mentioned in the My Oracle Support Document ID 2955825.1, perform these additional checks and configuration:

      1. Check the DOMAIN_HOME/init-info/config-path.properties file for the following entry. This entry could be different depending upon the patch level applied.

         For example: log4j_jar\#1.3@1.2.15=oracle.sysman.fmw.core_12.2.1.4.0/em_ORACLE_HOME or log4j_jar#2.17.1@2.17.1=oracle.sysman.fmw.core_12.2.1.4.0/em_ORACLE_HOME

      2. In the DOMAIN_HOME/config/config.xml file, add one of the following entries, which synchronizes with the above version.

         <library>
         <name>log4j_jar#1.3@1.2.15</name>
         <target>AdminServer</target>
         <source-path>[ORACLE_HOME path]/em/../oracle_common/modules/com.bea.core.apache.log4j.jar</source-path>
         <security-dd-model>DDOnly</security-dd-model>
         <staging-mode>nostage</staging-mode>
         </library>

         or

         <library>
         <name>log4j_jar#2.17.1@2.17.1</name>
         <target>AdminServer</target>
         <source-path>[ORACLE_HOME path]/em/../oracle_common/modules/com.bea.core.apache.log4j.jar</source-path>
         <security-dd-model>DDOnly</security-dd-model>
         <staging-mode>nostage</staging-mode>
         </library>

   5. Start all services.
      • In Linux, DOMAIN_HOME/bitools/bin/start.sh
      • In Windows, DOMAIN_HOME/bitools/bin/start.cmd
   6. Set the deployment status of Enterprise Manager to "Active".
      1. Log in to the WebLogic administration console as an administrator.
      2. Check if the Deployment status for "em" is "Active" or "Prepared". If the status is "Prepared", start the deployment to change the status to "Active".
3. In ODI Studio, navigate from Topology, Physical Architecture, to Technologies, and then click File to make sure the files of the technology data servers are under the new Oracle Home.
   If the registered files of all the applicable technology data servers are under the old Oracle Home, update the registered files to use the new Oracle Home.
4. Remove the old Oracle Home.
5. Run the loads to verify that everything is working as expected.
6. Drop the old Oracle Home.