Upgrade Fails if /export Is Near Capacity (4409601)

If the /export directory is near full capacity and you upgrade to the Solaris 9 operating environment, the space requirements for /export are miscalculated and the upgrade fails. The problem commonly occurs if a diskless client is installed, or if third-party software is installed in /export. The following message is displayed:

WARNING: Insufficient space for the upgrade.

Workaround: Before you upgrade, choose one of the following workarounds.

• Temporarily rename the /export directory until the upgrade is completed.

• Temporarily comment out the /export line in the /etc/vfstab file until the upgrade is completed.

• If /export is a separate file system, then unmount /export before you perform the upgrade.

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients that were installed with the AdminSuite 2.3 Diskless Client tool, you must first delete all existing diskless clients that are the same Solaris version and architecture as the server. Then, install or upgrade to the Solaris 9 operating environment. For specific instructions, see System Administration Guide: Basic Administration.

If you attempt to install the Solaris 9 operating environment over existing diskless clients, the following error message might appear:

The Solaris Version (Solaris version-number) on slice <xxxxxxxx> cannot be upgraded. There is an unknown problem with the software configuration installed on this disk.

In this error message, version-number refers to the Solaris version that is currently running on your system. <xxxxxxxx> refers to the slice that is running this version of the Solaris operating environment.

Upgrading the JavaSpaces Data Store to Prevent WBEM Data Loss (4365035)

If you are upgrading from the Solaris 8, Solaris 8 6/00, or Solaris 8 10/00 operating environments to the Solaris 9 operating environment (Solaris WBEM Services 2.5), you must convert any proprietary custom Managed Object Format (MOF) data to the new Reliable Log repository format that is used with Solaris WBEM Services 2.5. Failure to convert the data results in data loss.

See "Upgrading the CIM Object Manager Repository" in Solaris WBEM Services Administration Guide for specific instructions on how to convert your WBEM data.

64-Bit Solaris Issues

Sun UltraSPARC System (sun4u) Might Need Boot Flash PROM Update

Note - If your system is already running 64-bit ready firmware, then the flash PROM update is not required.

If you want to run the 64-bit Solaris operating environment on an UltraSPARC system, you might need to update its flash PROM firmware. The Solaris 9 installation programs enable you to add 64-bit support. This 64-bit support is selected by default when you install on Sun UltraSPARC™ systems. A 64-bit system only boots in the 64-bit mode by default if it has a CPU speed of 200 MHz or greater.

Note - If you choose to run the 32-bit Solaris operating environment on any Sun™ or UltraSPARC system, the flash PROM update is not needed.

The following table lists the UltraSPARC (sun4u) systems that are affected and the minimum firmware versions that are needed. System type is the equivalent of the output of the uname -i command. You can determine which firmware version you are running by using the prtconf -V command.

Table 1-2 Minimum Firmware Versions Required to Run 64-Bit Solaris Operating Environment on UltraSPARC Systems

Note - If a system is not listed in the previous table, it does not need a flash PROM update.

For instructions on performing the flash PROM update by using the Solaris CD, refer to the Solaris 9 on Sun Hardware Collection. If you do not have this manual, you can obtain it at http://docs.sun.com.

Documentation CD Issues

Cannot Install Documentation Packages With Names Longer Than Nine Characters on Documentation Servers Running the Solaris 2.6, 7, and 8 Operating Environments

Some localized documentation collections in PDF format have package names that are longer than nine characters. To install these PDF collections on servers that are running the Solaris 7 or 8 operating environment, you must first install two patches.

Note - No patches exist at the time of this release for Solaris 2.6 servers.

Workaround: For instructions on how to install these patches, see the Solaris Documentation Important Information file on the documentation media (Solaris 9 Documentation CD 1 of 2, 2 of 2, or DVD.) This file is located in the following directory:

mount-point/README/locale/install_locale.html

For example, the English file on the Solaris 9 Documentation CD 1 of 2 is located in the following directory:

sol_9_doc_1of2/README/C/install_C.html

Documentation CD Installation Bug

Documentation CD Verify Panel Might Not Page in Command Line Interface Mode (4520352)

If you use the Solaris 9 Documentation CD installer program with the -nodisplay option, the verify panel might not page correctly.

Workaround: Do not specify the -nodisplay option with the Solaris 9 Documentation CD installer program. Use the graphical user interface (GUI) mode to install the Solaris 9 Documentation CD.