E Deinstallation and Reinstallation

This appendix guides you through the deinstallation and reinstallation process for Oracle Application Server.

Section E.1, "New Tool: Deconfig Tool"
Section E.2, "Deinstallation Procedure:Overview"
Section E.3, "Deinstalling OracleAS Cold Failover Cluster Installations"
Section E.4, "Deinstalling Middle Tiers"
Section E.5, "Deinstalling OracleAS Infrastructure"
Section E.6, "Deinstalling OracleAS Developer Kits"
Section E.7, "Harmless Errors in the Log File"
Section E.8, "Cleaning Up Oracle Application Server Processes"
Section E.9, "Reinstallation"
Section E.10, "Troubleshooting"

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.

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, the tool prompts you for the necessary information.

E.1.1 Parameters

-u oid_user

Specify the Oracle Internet Directory user.

You can specify the Oracle Internet Directory user using the user's simple name or the user's distinguished name (DN). For example, the user's simple name can be jdoe@mycompany.com, which corresponds to the DN cn=jdoe,l=us,dc=mycompany,dc=com.

The Oracle Internet Directory user needs to have privileges for deinstalling the components that are configured in the Oracle Application Server instance that you want to deinstall. These privileges are the same as for installing and configuring the component.

For example, if you are deinstalling an OracleAS Infrastructure instance that is running Oracle Delegated Administration Services and OracleAS Single Sign-On, make sure the user has privileges to configure these components. For a list of components and groups that grant the privileges, see Section 8.3, "Groups Required to Configure or Deinstall Components".

If you want to run the tool as the Oracle Internet Directory superuser, be sure to use cn=orcladmin, and not just orcladmin. These are two different users. If you want more details about these users, see Section 8.1, "Default Users in Oracle Internet Directory".

-w password

Specify the password for the Oracle Internet Directory user.

-r realm

Specify the realm in which to authenticate the user. This value is required only if your Oracle Internet Directory has more than one realm.

-dbp sys_db_password

Specify the password for the SYS user in the database. This is the OracleAS Metadata Repository database used by Oracle Internet Directory.

This value is required only if you are deinstalling an Identity Management-only instance that has Oracle Internet Directory configured.

If you specify this parameter and it is not needed, the password value is simply not used.

-help or -h

You can also run the Deconfig tool with the -h or -help parameter to display help:

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

E.1.2 Log Files Generated by the Deconfig Tool

The Deconfig tool writes its log file to the ORACLE_HOME/cfgtoollogs/DeconfigureWrapper.log file.

E.2 Deinstallation Procedure: Overview

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

Deinstall middle-tier instances first.
1. Run the Deconfig tool on the instance.
2. Run the installer and click the Deinstall Products button.
3. Clean up any remaining files.
Then deinstall OracleAS Infrastructure instances.
1. Run the Deconfig tool on the instance.
2. Run the installer and click the Deinstall Products button.
3. Clean up any remaining files.

Notes:

If you used OracleAS Metadata Repository Creation Assistant to install the OracleAS Metadata Repository on an existing database, and you want to remove the OracleAS Metadata Repository, select the "Remove" option in OracleAS Metadata Repository Creation Assistant. You can also use OracleAS Metadata Repository Creation Assistant to remove the registration from Oracle Internet Directory.
If you remove an infrastructure instance, all middle-tier instances that depend on that infrastructure will no longer work.

If you want to keep the middle-tier instances, you can configure them to use services from another infrastructure. See the Oracle Application Server Administrator's Guide for details.

Items to Remove or Clean Up

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

Table E-1 Items to Deinstall

Item to Clean Up	Tool to Use
Files from the Oracle home directory	Installer If the installer does not remove all the files, you can remove the remaining files using the `rm` command.
Entries for the deleted instance in the Inventory directory	Installer
Instance name from Farm page	Installer
Entries for the deleted instance in the `/var/opt/oracle` or `/etc` directory	You have to remove the entries manually. See: Step 7 if you are deinstalling middle tiers. Step 9 if you are deinstalling OracleAS Infrastructure. Step 6 if you are deinstalling OracleAS Developer Kits.
Entries for the deleted instance in Oracle Internet Directory	Deconfig tool

The 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:

Stop the clusterware agents or packages that monitor and fail over the environment. See your clusterware documentation for details.
Then perform the steps described in this appendix.

If you do not take the resources offline, the installer will hang during the deinstallation because the clusterware agents are trying to fail over the resources.

E.4 Deinstalling Middle Tiers

Log in as the operating system user who installed the instance you want to deinstall.
Stop all processes associated with the instance you want to deinstall.

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

Run the Deconfig tool.

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

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

Start the installer.

prompt> $ORACLE_HOME/oui/bin/runInstaller

Follow these steps in the 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 the installer when the deinstallation is complete.
Delete any remaining files in the deleted instance's Oracle home directory.
```
prompt> rm -rf $ORACLE_HOME
```
Remove the line for the deinstalled middle-tier from the /etc/oratab 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
```
Note that OracleAS Portal entries in Oracle Internet Directory are not removed by the Deconfig tool or the installer.
Note that OracleAS Portal entries in Oracle Internet Directory are not removed by the Deconfig tool or the installer.

E.5 Deinstalling OracleAS Infrastructure

This section describes how to deinstall OracleAS Infrastructure instances.

E.5.1 Deinstallation Order

The OracleAS Infrastructure instance could contain all the OracleAS Infrastructure components, or it could contain only a subset of the components, because you have a distributed OracleAS Infrastructure installation. Here are some common scenarios and their deinstallation order:

If you have an Identity Management + OracleAS Metadata Repository instance, you have only one instance to deinstall.

If you installed Identity Management and OracleAS Metadata Repository separately:

Deinstall the Identity Management instance.
Deinstall the OracleAS Metadata Repository.

If you have a distributed Identity Management:

Deinstall the instance(s) that are running OracleAS Single Sign-On, Oracle Delegated Administration Services, Oracle Directory Integration and Provisioning, and/or OracleAS Certificate Authority.
Deinstall the instance running Oracle Internet Directory.
Deinstall the OracleAS Metadata Repository.

E.5.2 Deinstallation Steps

Log in as the operating system user who installed the instance you want to deinstall.
If OracleAS Certificate Authority is configured on the instance you want to deinstall, run the following commands:
```
prompt> $ORACLE_HOME/oca/bin/ocactl stop
prompt> $ORACLE_HOME/oca/bin/cmdeinst ocaAdminPassword oidAdminPassword
```
Replace ocaAdminPassword with the password of the OracleAS Certificate Authority administrator.

Replace oidAdminPassword with the password of the Oracle Internet Directory user who installed OracleAS Certificate Authority. The user must belong to the following groups:
- Trusted Application Admins
- iAS Admins
- Repository Owners group for the metadata repository used by OracleAS Certificate Authority
The "ocactl stop" command stops OCA services. The cmdeinst command performs the following actions:
- removes OracleAS Certificate Authority entries from Oracle Internet Directory
- removes data from tables in the oca schema
- removes OracleAS Certificate Authority files created by the OracleAS Certificate Authority Configuration Assistant during installation
If Oracle Directory Integration and Provisioning is configured and running in the instance you want to deinstall, stop the Oracle Directory Integration and Provisioning server.

Ensure that Oracle Internet Directory is running.

You can stop Oracle Directory Integration and Provisioning by running the following command:
```
prompt> cd $ORACLE_HOME/bin
prompt> oidctl connect=db_connect_string server=odisrv instance=1 stop
```
db_connect_string is the service name as listed in the file ORACLE_HOME/network/admin/tnsnames.ora.

For any additional Oracle Directory Integration and Provisioning servers that you started, you must stop them too. See the instructions in the Oracle Identity Management Integration Guide.
If Oracle Internet Directory is configured as a replica, you need to delete this node from the directory replication group (DRG). See Chapter 25, "Oracle Internet Directory Replication Administration", in the Oracle Internet Directory Administrator's Guide for steps.
Run the Deconfig tool.
```
prompt> cd $ORACLE_HOME/bin
prompt> $ORACLE_HOME/perl/bin/perl deconfig.pl [parameters]
```
See Section E.1, "New Tool: Deconfig Tool" for parameter details. Note: If you are deinstalling an instance that includes the Oracle Internet Directory or OracleAS Single Sign-On components, you need to run the Deconfig tool as the Oracle Internet Directory superuser (cn=orcladmin). If the instance does not include Oracle Internet Directory or OracleAS Single Sign-On, then you need to run the tool as a user with the proper privileges, as shown in Table 8-4.

Start the installer.

prompt> $ORACLE_HOME/oui/bin/runInstaller

Follow these steps in the 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 the installer when the deinstallation is complete.
Delete any remaining files in the deleted instance's Oracle home directory.
```
prompt> rm -rf $ORACLE_HOME
```
Remove lines for the deinstalled infrastructure instance from the /etc/oratab file.

Towards the end of the file, you should see lines that specify the Oracle home directory. If you are deinstalling an infrastructure instance that contains a metadata repository, there will be two lines in the file:
- one line that begins with a *
- one line that begins with the database SID
You need to remove both lines.

For example, if the infrastructure instance is installed in /private1/infra, and it includes a metadata repository whose SID is asdb, the lines would look like the following:
```
asdb:/private1/infra:N
*:/private1/infra:N
```

E.6 Deinstalling OracleAS Developer Kits

Log in as the operating system user who installed OracleAS Developer Kits.
Stop all processes associated with the instance you want to deinstall.

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

Start the installer.

prompt> $ORACLE_HOME/oui/bin/runInstaller

Follow these steps in the 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 the installer when the deinstallation is complete.
Delete any remaining files in the deleted instance's Oracle home directory.
```
prompt> rm -rf $ORACLE_HOME
```
Remove the line for the deinstalled OracleAS Developer Kits from the /etc/oratab 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.7 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.8 Cleaning Up Oracle Application Server Processes

If you forgot to shut down Oracle Application Server processes before starting the installation, 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.9 Reinstallation

The 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.10 Troubleshooting

See Section G.4, "Deinstallation Problems and Solutions" for help with common deinstallation problems.