| Oracle® Application Server Installation Guide 10g (10.1.4.0.1) for HP-UX PA-RISC (64-Bit) Part Number B32097-01 |
|
|
View PDF |
| Oracle® Application Server Installation Guide 10g (10.1.4.0.1) for HP-UX PA-RISC (64-Bit) Part Number B32097-01 |
|
|
View PDF |
This appendix guides you through the deinstallation and reinstallation process for Oracle Application Server.
Section D.3, "Deinstalling OracleAS Cold Failover Cluster Installations"
Section D.5, "Deinstalling OracleAS Cluster (Identity Management)"
Section D.8, "Cleaning Up Oracle Application Server Processes"
In this release, there is a 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 F.4.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 Clusters, you will need to run the dcmctl removecluster command after deinstalling the instances. See Section D.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 all of the parameters, the tool prompts you for the necessary information.
|
Note: For security reasons, it is not recommended that you specify the password on the command line. The Deconfig tool will prompt you for the password if you do not specify it on the command line. |
-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 5.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 5.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 Oracle 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
Follow these high-level steps to deinstall Oracle Application Server:
Deinstall middle-tier instances first. See Oracle Application Server Installation Guide for the middle-tier platform and release for deinstallation instructions.
Run the Deconfig tool on the instance.
Run the installer and click the Deinstall Products button.
Clean up any remaining files.
Then deinstall OracleAS Infrastructure instances. The deinstallation details are provided later in this chapter.
Run the Deconfig tool on the instance.
Run the installer and click the Deinstall Products button.
Clean up any remaining files.
|
Note:
|
Items to Remove or Clean Up
To deinstall Oracle Application Server instances, you have to clean up the items listed in Table D-1. The procedures are described later in this appendix.
Table D-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 |
|
Entries for the deleted instance in the Inventory directory |
Installer |
|
Instance name from Farm page |
Installer |
|
Entries for the deleted instance in the |
You have to remove the entries manually. See:
|
|
Entries for the deleted instance in Oracle Internet Directory |
Deconfig tool |
The installer does not permit custom deinstallation of individual components.
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.
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 D.6, "Deinstalling OracleAS Infrastructure".
Open the file located at ORACLE_HOME/deconfig/DeconfigWrapper.properties for editing.
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%
Comment out the line by adding a pound (#) character at the beginning of the line. In the example above, 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 D.6, "Deinstalling OracleAS Infrastructure" to complete the deinstallation.
To deinstall an OracleAS Cluster (Identity Management), perform the following steps.
Deinstall all instances that contain OracleAS Single Sign-On except for the last instance installed. Use the steps in Section D.4, "Deinstalling OracleAS Single Sign-On Instances in OracleAS Cluster (Identity Management)" to perform the deinstallation.
Deinstall the last OracleAS Single Sign-On instance using the steps in Section D.6, "Deinstalling OracleAS Infrastructure".
If you are using a Distributed OracleAS Cluster (Identity Management), deinstall the Oracle Internet Directory instances using the steps in Section D.6, "Deinstalling OracleAS Infrastructure".
After deinstalling all instances, remove the OracleAS Cluster (Identity Management) from its farm by running the dcmctl removecluster command:
prompt> $ORACLE_HOME/dcm/bin/dcmctl removecluster -cl cluster_name
This section describes how to deinstall OracleAS Infrastructure instances. It includesthe following topics:
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 Oracle Identity Management + OracleAS Metadata Repository instance, you have only one instance to deinstall.
If you installed Oracle Identity Management and OracleAS Metadata Repository separately:
Deinstall the Oracle Identity Management instance.
Deinstall the OracleAS Metadata Repository.
If you have a distributed Oracle Identity Management:
Deinstall the instance(s) that are running OracleAS Single Sign-On, Oracle Delegated Administration Services, Oracle Directory Integration Platform, and/or OCA.
Deinstall the instance running Oracle Internet Directory.
Deinstall the OracleAS Metadata Repository.
Log in as the operating system user who installed the instance you want to deinstall.
If OCA 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 OCA administrator.
Replace oidAdminPassword with the password of the Oracle Internet Directory user who installed OCA. The user must belong to the following groups:
Trusted Application Admins
iAS Admins
Repository Owners group for the metadata repository used by OCA
The "ocactl stop" command stops OCA services. The cmdeinst command performs the following actions:
removes OCA entries from Oracle Internet Directory
removes data from tables in the oca schema
removes OCA files created by the OCA Configuration Assistant during installation
If Oracle Directory Integration Platform is configured and running in the instance you want to deinstall, stop the Oracle Directory Integration Platform server.
Ensure that Oracle Internet Directory is running.
You can stop Oracle Directory Integration Platform 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 TNS alias as listed in the file ORACLE_HOME/network/admin/tnsnames.ora.
For any additional Oracle Directory Integration Platform 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 D.1, "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 5-4.
Start the installer.
prompt> $ORACLE_HOME/oui/bin/runInstaller
Follow these steps in the installer.
Welcome screen: Click Deinstall Products.
Inventory screen: Select the instance you want to deinstall, and click Remove.
Confirmation screen: Verify the components selected for deinstallation. Click Yes to continue.
Deinstallation Progress screen: Monitor the progress of the deinstallation.
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 /var/opt/oracle/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 orcl, the lines would look like the following:
orcl:/private1/infra:N *:/private1/infra:N
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) ...
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.
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.
See Section F.4, "Deinstallation Problems and Solutions" for help with common deinstallation problems.
