Resolving Uninstallation Problems

This section addresses the following problems you might encounter during uninstallation.

• Cannot Find Uninstaller

• Uninstallation Fails, Leaving Behind Files

• Product Registry Is Corrupted

Cannot Find Uninstaller

The Java ES installation program places the uninstaller on your system at the following location:

• Solaris OS: /var/sadm/prod/SUNWentsys5u1

• Linux: /var/sadm/prod/sun-entsys5u1

If the uninstaller is not in this directory, one of the following might have occurred:

• Java ES was never installed on this host.

• The Java ES uninstaller previously removed all product components and itself from this host.

  During uninstallation, if the uninstaller detects that there are no Java ES product components on a host, it uninstalls itself.

• During a failed installation, one of the following occurred:

  • The uninstaller was never installed on the host.

  • The uninstaller was removed, but some Java ES product components remain on the host.

Suggested Fix. Manually clean up your system as described in Uninstallation Fails, Leaving Behind Files.

Uninstallation Fails, Leaving Behind Files

If manual cleanup is necessary because the uninstaller left behind files or processes, perform the following procedure to remove packages from your system.

To Manually Clean Up Packages

1. Determine which packages you want to remove.

   Compare the packages on your system with the Java ES packages listed in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX. (See also Installation Fails Due to Files Left Behind During an Uninstallation. You can use the following commands to determine which packages are installed:

   • Solaris OS: pkginfo or prodreg utility

   • Linux: rpm command

2. Stop all running processes for Java ES product components.

   Brief instructions for stopping processes are contained in Chapter 6, Completing Postinstallation Configuration product component documentation.

3. Back up all custom configuration and user data you plan to use in subsequent installations.

   Reviewing Uninstallation Behavior for Java ES Product Components provides some information on configuration and user data that should be backed up. For more information, refer to the product component documentation for each product component.

4. Use the pkgrm, rpm -e, or swremove command to remove Java ES component packages.

5. Remove any remaining product component directories and their content that you do not plan to use in subsequent installations. If you do plan to use these directories later, move them elsewhere.

6. Update the product registry file, which is located here:

   • Solaris OS: /var/sadm/install/productregistry

   • Linux: /var/opt/sun/install/productregistry

   The uninstaller uses this registry to determine which product components are installed on a host. Both the installer and uninstaller update the product registry upon completion of an installation or uninstallation.

   ---

   Note –

   If you manually remove packages rather than using the uninstaller, then you must edit the product registry so it correctly reflects the software installed on your system.

   ---

7. Clean up the log files for your system, which are located here:

   • Solaris OS: /var/sadm/install/logs

   • Linux: /var/opt/sun/install/logs

   The log files might not correctly reflect the state of your system after you manually remove packages.

Product Registry Is Corrupted

During uninstallation, the uninstaller uses the product registry file to determine what needs to be uninstalled:

• Solaris OS: /var/sadm/install/productregistry

• Linux: /var/opt/sun/install/productregistry

• If the uninstaller fails, you might need to retry after you restore the product registry from your backup copy.

• If you manually remove packages, the product registry is not automatically updated. When you subsequently run the uninstaller, you might encounter problems because the product registry does not correctly reflect your system. In this case, you can try to reinstall and then run the uninstaller again.