Oracle® Application Server 10g Installation Guide
10g (9.0.4) for hp HP-UX PA-RISC (64-bit) and Linux x86 Part No. B10842-03 |
|
![]() |
![]() |
This appendix guides you through the deinstallation and reinstallation process for Oracle Application Server.
Contents:
To deinstall Oracle Application Server instances, you have to clean up the items listed in Table C-1.
The installation procedures, described later in this appendix, provide steps on how to delete these items. They also provide details on how to clean up the items that require manual steps.
Table C-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 oraInventory directory | Installer |
Instance name from Farm page | Installer |
Entries for the deleted instance in the /var/opt/oracle directory on HP-UX
Entries in the |
You have to remove the entries manually. See: |
Entries for the deleted instance in Oracle Internet Directory | You have to remove the entries manually. See Section C.1.7, "Removing Entries for a Deleted Instance from Oracle Internet Directory". |
The installer does not permit custom deinstallation of individual components.
This section covers the following topics:
Section C.1.7, "Removing Entries for a Deleted Instance from Oracle Internet Directory"
Section C.1.8, "Removing Oracle Ultra Search Entries from Oracle Internet Directory"
Section C.1.9, "Cleaning Up Oracle Application Server Processes"
In Release 2 (9.0.2), if you have multiple Oracle9iAS instances installed on a computer, one of them was designated the primary installation. The primary installation contained the active Oracle Enterprise Manager. If you deinstall the primary installation, the installer prompts you designate one of the remaining Oracle9iAS instances to be the primary installation.
In 10g (9.0.4), there is no concept of primary installation. All instances on a computer have their own Oracle Enterprise Manager.
If you remove an infrastructure instance, all middle tier instances that depend on that infrastructure will no longer work. If you want to remove both infrastructure and middle tiers associated with it, deinstall all the middle tiers first, then deinstall the infrastructure.
If you want to keep the middle tier instances, you can configure them to use services from another infrastructure. See the Oracle Application Server 10g Administrator's Guide for details.
If you deinstall a middle tier instance that uses an infrastructure, you cannot reuse the name of the deinstalled instance when installing subsequent middle tier instances. To reuse the instance name, you must delete the entry for the deinstalled instance from Oracle Internet Directory.
Log in as the operating system user who installed the instance you want to deinstall.
De-register the middle tier from OracleAS Single Sign-On.
The command for de-registration is similar to the command for registration, except that the -update_mode
parameter is set to DELETE
.
Make sure the shared library path environment variable contains $ORACLE_HOME/lib
.
Table 4-15 lists the shared library path environment variables for different platforms
Then run the command (all on one line):
prompt> $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar -oracle_home_path $ORACLE_HOME -site_name hostname.domain -config_mod_osso TRUE -mod_osso_url http://hostname.domain:port -u userid -update_mode DELETE
For -site_name
hostname.domain, specify the computer where the middle tier is installed. Include also the domain name.
For -mod_osso_url http://
hostname.domain:port, specify the computer where the middle tier is installed, and the port number on which Oracle HTTP Server is listening.
For -u
userid, specify the operating system user who can start up the middle tier processes.
For a detailed explanation of the parameters, see chapter 4 of the Oracle Application Server Single Sign-On Administrator's Guide.
Stop all processes associated with the instance you want to deinstall.
See the Oracle Application Server 10g 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.
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 the line for the deinstalled middle tier from the /var/opt/oracle/oratab
file on HP-UX and the /etc/oratab
file on Linux.
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
Remove entries for the deinstalled middle tier from Oracle Internet Directory. You have to perform this step if you want to reuse the instance name. See Section C.1.7, "Removing Entries for a Deleted Instance from Oracle Internet Directory".
Log in as the operating system user who installed the instance you want to deinstall.
If you did not install OracleAS Certificate Authority, skip this step and go to step 3. If you installed OracleAS Certificate Authority, you have to run the following script.
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 script 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
Stop all processes associated with the instance you want to deinstall.
See the Oracle Application Server 10g 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.
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 on HP-UX and the /etc/oratab
file on Linux.
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
Remove entries for the deinstalled infrastructure instance from Oracle Internet Directory. You have to perform this step if you want to reuse the instance name.
See Section C.1.7, "Removing Entries for a Deleted Instance from Oracle Internet Directory".
Remove entries for Oracle Ultra Search from Oracle Internet Directory. You have to perform this step if you want to reuse the database name or SID.
See Section C.1.8, "Removing Oracle Ultra Search Entries from Oracle Internet Directory".
If you are deinstalling the metadata repository but plan to reuse the Oracle Internet Directory, you should remove the metadata repository registration from Oracle Internet Directory. Follow the steps in Section 10.11, "Cleaning Up a Failed Registration or Deregistering a Metadata Repository".
Log in as the operating system user who installed OracleAS Developer Kits 10g.
Stop all processes associated with the instance you want to deinstall.
See the Oracle Application Server 10g 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.
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 the line for the deinstalled OracleAS Developer Kits 10g from the /var/opt/oracle/oratab
file on HP-UX and the /etc/oratab
file on Linux.
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
To remove entries for a deleted instance from Oracle Internet Directory, perform these steps:
Start up Oracle Directory Manager. Oracle home refers to the home where you installed Oracle Internet Directory.
prompt> $ORACLE_HOME/bin/oidadmin
In the Connect screen, enter the Oracle Internet Directory connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin
).
Expand the following entries:
Expand "Entry Management".
Expand "cn=OracleContext".
Expand "cn=Products".
Expand "cn=IAS".
Expand "cn=IAS Instances".
Under "cn=IAS Instances", select the instance that you want to delete.
From the menu, select Edit > Delete.
Expand the following entries:
Expand "Entry Management".
Expand "cn=OracleContext".
Expand "cn=Groups".
Select "cn=IASAdmins".
In the Properties tab, remove the instance from the uniquemember
field by editing the field. Do not select Edit > Delete from the menu.
Click Apply.
You need to remove Oracle Ultra Search entries from Oracle Internet Directory if you want to install another Oracle Application Server instance using the same database name or SID.
Start up Oracle Directory Manager. Oracle home refers to the home where you installed Oracle Internet Directory.
prompt> $ORACLE_HOME/bin/oidadmin
In the Connect screen, enter the Oracle Internet Directory connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin
).
Expand the following entries:
Expand "Entry Management".
Expand "cn=OracleContext".
Expand "cn=Products".
Expand "cn=Portal".
Expand "cn=UltraSearch".
Expand "cn=Database Instances".
Expand "orclApplicationCommonName=infrastructure_database_name".
Delete all the child entries under "orclApplicationCommonName=infrastructure_database_name", starting with the inner-most child entry. To delete an entry, right-click each child entry and select Delete from the pop-up menu. Click Yes in the Confirmation dialog. When deleting child entries, you may get some error messages. You can ignore these error messages.
After you have deleted all the entries under "orclApplicationCommonName=infrastructure_database_name", right-click this entry and delete it.
Expand the following entries:
Expand "Entry Management".
Expand the Default Subscriber entry. You need to expand each term separately. For example: if your default subscriber is "dc=us,dc=oracle,dc=com", you need to expand "dc=com", then expand "dc=oracle", then expand "dc=us".
Expand "cn=OracleContext".
Expand "cn=Products".
Expand "cn=Portal".
Expand "cn=UltraSearch".
Expand "cn=Database Instances".
Expand "cn=infrastructure_database_name".
Delete all the child entries under "cn=infrastructure_database_name", starting with the inner-most child entry. To delete an entry, right-click each child entry and select Delete from the pop-up menu. Click Yes in the Confirmation dialog. When deleting child entries, you may get some error messages. You can ignore these error messages.
After you have deleted all the entries under "cn=infrastructure_database_name", right-click this entry and delete it.
Click Apply.
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
.
If you have 9.0.2 or 9.0.3 and 10g (9.0.4) instances on the same computer, and you want to deinstall a 9.0.2 or 9.0.3 instance, perform these steps:
Apply patch 3234681 to your 9.0.2 or 9.0.3 instances. You can download the patch from OracleMetaLink (http://metalink.oracle.com
).
See Section C.2.1, "Issue: 10g (9.0.4) Instance Must Not Contain the Active Oracle Enterprise Manager" for details on why you need this patch.
Stop all processes associated with the instance you want to deinstall.
Run the installer to deinstall the 9.0.2 or 9.0.3 instance. Make sure you run the installer for the 9.0.2 or 9.0.3 instance. For 9.0.2 and 9.0.3 instances, the installer is located in the oui/install
directory at the same level as the Oracle home directory. For example, if the 9.0.2 or 9.0.3 Oracle home is /opt/oracle/orahome902
, then the installer would be /opt/oracle/oui/install/runInstaller
.
If you have multiple 9.0.2 and/or 9.0.3 instances on the same computer, these instances share an Oracle Enterprise Manager. This is the "active Oracle Enterprise Manager". When you deinstall the instance that contains the active Oracle Enterprise Manager using the installer, the installer needs to switch the active Oracle Enterprise Manager to one of the remaining instances. If there is only one remaining instance, then the installer automatically makes it the active Oracle Enterprise Manager. If more than one instance remain, the installer prompts you to select the instance to contain the active Oracle Enterprise Manager.
Unlike 9.0.2 or 9.0.3 instances, Oracle Application Server 10g (9.0.4) instances on the same computer do not share an Oracle Enterprise Manager. Each 10g (9.0.4) instance has its own Oracle Enterprise Manager.
Because 10g (9.0.4) instances do not share an Oracle Enterprise Manager, you must not select a 10g (9.0.4) instance to contain the active Oracle Enterprise Manager. You must select a 9.0.2 or 9.0.3 instance to contain the active Oracle Enterprise Manager.
If you select a 10g (9.0.4) instance, or if the installer automatically switches the active Oracle Enterprise Manager to a remaining instance that happens to be a 10g (9.0.4) instance, the installer overwrites files in the 10g (9.0.4) Oracle home with files from the 9.0.2 or 9.0.3 home. This causes Oracle Enterprise Manager to stop working.
The patch prevents the installer from automatically switching the active Oracle Enterprise Manager to a 10g (9.0.4) instance in the case where the only remaining instances are 10g (9.0.4) instances. It also prevents the installer from displaying 10g (9.0.4) instances in the list where you select the instance to contain the active Oracle Enterprise Manager.
If a 10g (9.0.4) instance becomes the active Oracle Enterprise Manager, Oracle Enterprise Manager will stop working.
To fix this, perform these steps in the 10g (9.0.4) Oracle home:
Shut down the Oracle Enterprise Manager Application Server Control.
prompt> emctl stop iasconsole
Rename the following files. Do not delete the files, because you might need them in step 5. You can rename them with an "active
" suffix (for example, iasadmin.properties.active
):
ORACLE_HOME/sysman/config/iasadmin.properties
ORACLE_HOME/sysman/emd/targets.xml
ORACLE_HOME/sysman/j2ee/config/jazn-data.xml
ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml
Copy the backup files for the files listed in the preceding step.
The backup files are in the same directory as the listed files. The names of the backup files are suffixed with a digit (for example, iasadmin.properties.1
). Check the timestamp, or check the content, of the backup files to determine the most recent backup file.
Start the Oracle Enterprise Manager Application Server Control.
prompt> emctl start iasconsole
If you have remaining 9.0.2/9.0.3 instances on the computer, you need to designate one of them to contain the active Oracle Enterprise Manager.
Copy the files listed in step 2 (which you renamed with the active
suffix) to the 9.0.2/9.0.3 instance’s Oracle home. Rename them back to the original names (that is, remove the active
suffix).
Edit the /var/opt/oracle/emtab
file on HP-UX and the /etc/emtab
file on Linux to set the DEFAULT
property to refer to the new active Oracle Enterprise Manager.
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.
If you deinstall a middle tier instance that uses an OracleAS Infrastructure 10g, you cannot reuse the name of the deinstalled instance when installing subsequent middle tier instances. To reuse the instance name, you must delete the entry for the deinstalled instance from Oracle Internet Directory.