E Deinstallation and Reinstallation

E.1 New Tool: Deconfig Tool

In this release, there is a new tool called the Deconfig tool that you need to run as part of the deinstallation procedure. This tool removes entries in OracleAS Metadata Repository and Oracle Internet Directory for the Oracle Application Server instance that you want to deinstall.

The Deconfig tool does not remove partner application entries. If you need to remove partner application entries, follow the steps in Section G.3.1, "Obsolete Partner URLs Still Remain on the OracleAS Single Sign-On Administration Screen".

The Deconfig tool does not remove OracleAS Clusters from the farm. If you are deinstalling OracleAS Cluster, you will need to run the dcmctl removecluster command after deinstalling the instances. Refer to Section E.5, "Deinstalling OracleAS Cluster (Identity Management)"for details.

To run the Deconfig tool, run the Perl interpreter on the ORACLE_HOME/bin/deconfig.pl script. Use the Perl interpreter provided with Oracle Application Server.

prompt> cd $ORACLE_HOME/bin
prompt> $ORACLE_HOME/perl/bin/perl deconfig.pl [-u oid_user]
            [-w password] [-r realm] [-dbp sys_db_password]

If you run it without any parameters, then the tool prompts you for the necessary information.

prompt> $ORACLE_HOME/perl/bin/perl deconfig.pl -h
 - or -
prompt> $ORACLE_HOME/perl/bin/perl deconfig.pl -help

E.2 Deinstallation Procedure: Overview

Follow these high-level steps to deinstall Oracle Application Server (the details are provided in later sections):

1. Deinstall middle-tier instances first.

   1. Run the Deconfig tool on the instance.

   2. Run Oracle Universal Installer and click the Deinstall Products button.

   3. Clean up any remaining files.

2. Then deinstall OracleAS Infrastructure instances.

   1. Run the Deconfig tool on the instance.

   2. Run Oracle Universal Installer and click the Deinstall Products button.

   3. Clean up any remaining files.

Items to Remove or Clean Up

To deinstall Oracle Application Server instances, you have to clean up the items listed in Table E-1. The procedures are described later in this appendix.

Oracle Universal Installer does not permit custom deinstallation of individual components.

E.3 Deinstalling OracleAS Cold Failover Cluster Installations

If you are deinstalling an OracleAS Cold Failover Cluster installation:

1. Stop the clusterware agents or packages that monitor and fail over the environment. Refer to your clusterware documentation for details.

2. Then perform the steps described in this appendix.

E.4 Deinstalling OracleAS Single Sign-On Instances in OracleAS Cluster (Identity Management)

If you have multiple OracleAS Single Sign-On instances installed in a cluster against the same Oracle Internet Directory and you would like to deinstall some of the instances but keep others running, perform the following steps before running the Deconfig tool.

Note that if the OracleAS Single Sign-On instance that you wish to deinstall was the last instance to be installed against the Oracle Internet Directory, you should not perform this step. Instead, perform the steps in Section E.7, "Deinstalling OracleAS Infrastructure".

1. Open the file located at ORACLE_HOME/deconfig/DeconfigWrapper.properties for editing.

2. Search for the line that begins with "SSO=". For example, the line might look like the following:

   SSO=/OraHome_1/jdk/bin/java -jar /OraHome_1/sso/lib/ossoca.jar deinstall /OraHome_1 "%OID_USER%" %OID_PASSWORD%
   
   

3. Comment out the line by adding a pound (#) character at the beginning of the line. In the preceding example, the line would be changed to look like the following:

   # SSO=/OraHome_1/jdk/bin/java -jar /OraHome_1/sso/lib/ossoca.jar deinstall /OraHome_1 "%OID_USER%" %OID_PASSWORD%
   
   

After modifying the file, perform the steps in Section E.7, "Deinstalling OracleAS Infrastructure" to complete the deinstallation.

E.5 Deinstalling OracleAS Cluster (Identity Management)

To deinstall an OracleAS Cluster (Identity Management), perform the following steps.

1. Deinstall all instances that contain OracleAS Single Sign-On except for the last instance installed. Use the steps in Section E.4, "Deinstalling OracleAS Single Sign-On Instances in OracleAS Cluster (Identity Management)" to perform the deinstallation.

2. Deinstall the last OracleAS Single Sign-On instance using the steps in Section E.7, "Deinstalling OracleAS Infrastructure".

3. If you are using a Distributed OracleAS Cluster (Identity Management), deinstall the Oracle Internet Directory instances using the steps in Section E.7, "Deinstalling OracleAS Infrastructure".

E.6 Deinstalling Middle Tiers

To deinstall middle tiers:

1. Log in as the operating system user who installed the instance you want to deinstall.

2. Stop all processes associated with the instance you want to deinstall.

   Refer to Oracle Application Server Administrator's Guide for details on how to stop the processes.

3. Run the Deconfig tool.

   prompt> cd $ORACLE_HOME/bin
   prompt> $ORACLE_HOME/perl/bin/perl deconfig.pl [parameters]
   
   

   Refer to Section E.1, "New Tool: Deconfig Tool" for parameter details.

4. Start Oracle Universal Installer.

   prompt> $ORACLE_HOME/oui/bin/runInstaller
   
   

5. Follow these steps in Oracle Universal Installer.

   1. Welcome screen: Click Deinstall Products.

   2. Inventory screen: Select the instance you want to deinstall, and click Remove.

   3. Confirmation screen: Verify the components selected for deinstallation. Click Yes to continue.

   4. Deinstallation Progress screen: Monitor the progress of the deinstallation.

   5. Exit Oracle Universal Installer when the deinstallation is complete.

6. Delete any remaining files in the Oracle home directory of the deleted instance.

   prompt> rm -rf $ORACLE_HOME
   
   

7. Remove the line for the deinstalled middle tier from the file.

   Towards the end of the file, you should see lines that specify the Oracle home directory. Remove the line for the Oracle home that you deinstalled. For example, if your Oracle home is /private1/j2ee, the line would look like the following:

   *:/private1/j2ee:N
   
   

8. Note that OracleAS Portal entries in Oracle Internet Directory are not removed by the Deconfig tool or Oracle Universal Installer.

E.7 Deinstalling OracleAS Infrastructure

This section describes how to deinstall OracleAS Infrastructure instances. It includes the following topics:

• Section E.7.1, "Deinstallation Order"

• Section E.7.2, "Deinstallation Steps"

E.8 Deinstalling OracleAS Developer Kits

1. Log in as the operating system user who installed OracleAS Developer Kits.

2. Stop all processes associated with the instance you want to deinstall.

   Refer to Oracle Application Server Administrator's Guide for details on how to stop the processes.

3. Start Oracle Universal Installer.

   prompt> $ORACLE_HOME/oui/bin/runInstaller
   
   

4. Follow these steps in Oracle Universal Installer.

   1. Welcome screen: Click Deinstall Products.

   2. Inventory screen: Select the instance you want to deinstall, and click Remove.

   3. Confirmation screen: Verify the components selected for deinstallation. Click Yes to continue.

   4. Deinstallation Progress screen: Monitor the progress of the deinstallation.

   5. Exit Oracle Universal Installer when the deinstallation is complete.

5. Delete any remaining files in the Oracle home directory of the deleted instance.

   prompt> rm -rf $ORACLE_HOME
   
   

6. Remove the line for the deinstalled OracleAS Developer Kits from the file.

   Towards the end of the file, you should see lines that specify the Oracle home directory. Remove the line for the Oracle home that you deinstalled. For example, if your Oracle home is /private1/devkit, the line would look like the following:

   *:/private1/devkit:N
   
   

E.9 Harmless Errors in the Log File

If you get the following "unable to delete file" and "unable to find make file" errors in the oraInstalltimestamp.err file after you deinstall J2EE and Web Cache or Portal and Wireless instances, these are harmless error messages.

Ignoring Exception during de-install oracle.sysman.oii.oiil.OiilDeinstallException:
An error occurred during runtime. oracle.sysman.oii.oiil.OiilDeinstallException:
An error occurred during runtime.
...
Ignoring Exception during de-install oracle.sysman.oii.oiil.OiilDeinstallException:
Unable to delete file 
/home/j2ee/sysman/emd/targets.xml
oracle.sysman.oii.oiil.OiilDeinstallException: Unable to delete file
/home/j2ee/sysman/emd/targets.xml
at instantiateFileEx.deinstallAction(instantiateFileEx.java:935)
...
Ignoring Exception during de-installoracle.sysman.oii.oiil.OiilDeinstallException:
Unable to find make file:
/home/j2ee/network/lib/ins_net_client.mk
oracle.sysman.oii.oiil.OiilDeinstallException: Unable to find make file:
/home/j2ee/network/lib/ins_net_client.mk
at ssmakeux.deinstallAction(ssmakeux.java:246)
...

E.10 Cleaning Up Oracle Application Server Processes

If you do not shut down Oracle Application Server processes before starting the installation, then you have to kill the processes because the files for these processes are deleted. To check for processes that are still running, run the ps command:

prompt> ps -ef

To kill a process, use the kill command:

prompt> kill -9 process_id

You can determine the process_id from the ps command.

If you need to shut down the dcmctl shell process, you can try exiting the shell by typing exit.

E.11 Reinstallation

Oracle Universal Installer does not allow reinstallation of an Oracle Application Server instance in a directory that already contains an Oracle Application Server instance. To reinstall Oracle Application Server in the same directory, you have to deinstall and then install it.

E.12 Troubleshooting

Refer to Section G.3, "Deinstallation Problems and Solutions" for help with common deinstallation problems.