General Installation Issues

After installing a component with the Java ES installer, you must use the uninstaller to uninstall (no bug number)

If you remove component packages or RPMs directly, the next time the installer is run, it may see a component as still being installed and not behave correctly.

Solution If you have already removed component packages or RPMs manually, you must still use the Java ES uninstaller to uninstall the component.

In CLI mode the Java ES installer continues even when it lacks swap space (6436570)

If the system on which you run the Java ES installer does not have sufficient swap space to run the installer, the CLI mode installer (./installer -nodisplay) continues to run after displaying an error message that includes:

com.sun.entsys.dre.DREException: Not enough space

Solution If you see this message, exit the installer. Then, allocate more swap space or free up existing swap space before running the installer again.

On Solaris 10, installation in a whole root zone is unsuccessful (6451030)

When installing Java ES in a whole root zone on earlier versions of Solaris 10, the installer might display one of these messages:

Unsupported components in zone
Following components required by the selected components, are not 
supported in local zone and they can not be installed directly into 
the local zone. Please install these components from the global zone 
before proceeding the installation

     SharedComponent

or

The Sun Web Console packages that are installed on your system
have a defect that is preventing Java ES from installing in a
while root non-global zone. In order to rectify this situation
you must upgrade the Sun Web Console packages in the global zone
before installing Java ES in a whole root zone. Please see the
Java ES Release Notes (bug 6451030) and Installation Guide for
further information.

Both of these messages appear because the Sun Java Web Console packages already installed contain an incorrect attribute setting that prevents the installer from upgrading them. The Sun Java Web Console packages that contain the incorrect attribute setting were shipped with Solaris 10, Solaris 10 1/06, Solaris 10 6/06, and Java ES 2005Q4.

Solution To resolve this issue, you must upgrade the Sun Java Web Console packages in the global zone before you install Java ES in a whole root zone. You have two options:

• In the global zone, run the installer and install only All Shared Components. This upgrades the Sun Java Web Console packages and fixes the zones attribute, but also installs all the other Java ES 5 shared components into the global zone and propagates them into all non-global zones. This might not be acceptable for your situation and is not recommended if you have a previous version of Java ES installed in a whole root zone.

• In the global zone, upgrade only the Sun Java Web Console packages. To do this, log into the global zone and navigate to the Java ES 5 installation directory for Solaris. As root, do the following:

  cd Product/sunwebconsole ./setup

  The setup script upgrades Sun Java Web Console in the global zone and propagates the upgrade to all non-global zones.

On HP-UX, performance issue with Java ES installer (6472918)

The Java ES installer interacts with the HP-UX depot mechanism to find installed components, check for dependencies, and install the bits. The client-server architecture of the depot mechanism leads to slower system response time, and the repeated interaction makes the overall installation process noticeably slower than on other platforms.

Solution None.

Installer does not report component configuration failures due to a low file descriptor limit (5018734, 6523904)

If the system has a file descriptor limit of set too low, some components cannot be configured correctly. The installer does not report such configuration failures, but the configuration log files show the failures.

Solution Before installation, set the file descriptor limit to a high value, such as 1024 or 2048. After installation, you can reset the file descriptor limit back to its previous value.

Java ES Installer needs a mechanism to query if a product license is of type evaluation (6265136)

The installer should check if shared components is an evaluation component and replace it if in fact it is an evaluation component.

Solution Ensure that the workstation does not have an evaluation component installed before beginning an installation.

Zone improvement and physical media installation (6298792)

Any Java ES 2005Q4 installation using CD swaps from within zones will fail. Installation into non-global zones from CDs is not supported in Java ES 2005Q4. Specifically, installation of Sun Cluster on a local zone is also not supported.

Installer requests patch that is not applicable on Solaris 9, update 6 (6315304)

When installing build 10 on Solaris 9, update 6 the install fails because it requires a patch that is not applicable on update 6 (patch 117714–06).

Solution Install the SUNWced and SUNWcedu packages.

Installation log messages are not always valid (no bug number)

Please note that log messages are not always valid. For example, the “no software was installed” message appears even if some (but not all) component products are installed after an error of some sort.

Auto-selection of components in component selection page confusing (4957873)

When a component product is selected, the installer automatically selects to install any dependent component products. The component product selection page does not indicate that the dependencies have been selected along with the original component product.

Solution None.

Insufficient window width in interface for some locales (4949379)

The window for certain languages like German is not wide enough to display the entire interface. As a result, text of elements like hints get truncated at the right hand side or at the bottom.

Solution Manually resize the window.