test

Solaris 8 (Intel Platform Edition) 1/01 Release Notes Update

Installation Bugs That Occur During an Upgrade

Caution - Caution -

Be sure to read bug description ID 4121281 before you start upgrading your IA (Intel architecture) based system to the Solaris 8 operating environment.

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients installed with the AdminSuite 2.3 Diskless Client tool, you must first delete all existing diskless clients prior to installing the Solaris 8 1/01 operating environment. For specific instructions, see "How to Set Up Your Diskless Client Environment" in Solaris 8 System Administration Supplement.

If you attempt to install the Solaris 8 1/01 operating environment over existing diskless clients, the following error message appears:


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

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

If you are upgrading from the Solaris 8 (Solaris WBEM Services 2.0), Solaris 8 6/00 (WBEM Services 2.1), or Solaris 8 10/00 (WBEM Services 2.2) operating environments to the Solaris 8 1/01 operating environment (Solaris WBEM Services 2.3), you must convert any proprietary custom Managed Object Format (MOF) data to the new Reliable Log repository format used with Solaris WBEM Services 2.3. Failure to convert the data will result in data loss.

Workaround: To convert WBEM data, before upgrading you must save the JavaSpacesTM software. After upgrading, you must run the wbemconfig convert command.

Before upgrading to the Solaris 8 1/01 operating environment, follow these steps to save the JavaSpaces software.

  1. Become superuser.

  2. Save the JavaSpaces software.

    cp /usr/sadm/lib/wbem/outrigger.jar /usr/sadm/lib/wbem/outrigger.jar.tmp

  3. Check and record the version of the JDKTM software installed on your machine. For example:

    # /usr/bin/java -version java version "1.2.1" Solaris VM (build Solaris_JDK_1.2.1_04c, native threads, sunwjit)

    You must be running the same version of the JDK software that was running when the original JavaSpaces datastore was created.

Note -

After upgrading to the Solaris 8 1/01 operating environment, you must convert the WBEM data. For specific instructions, see Solaris 8 Installation Supplement.

DiskSuite May Cause Data Loss (4121281)

The DiskSuiteTM metadb replicas contain driver names as part of the DiskSuite configuration data. In IA-based systems that run versions 2.4, 2.5, 2.5.1, and 2.6 of the Solaris operating environment, the SCSI driver name is cmdk. The cmdk driver has been replaced by the sd driver in the Solaris 7 and 8 operating environments for IA-based systems.

Workaround: To avoid potential data loss during upgrades to the Solaris 7 and 8 operating environments, you must save the system's meta device configurations in text files and remove their metadb replicas before upgrading any IA-based system that is running DiskSuite software. After you finish upgrading your IA-based system, you must restore the meta device configurations by using the DiskSuite command line interface.

The DiskSuite Version 4.2 Release Notes describe a procedure for saving metadb configurations, removing metadb replicas, upgrading IA-based systems to the Solaris 7 and 8 operating environments, upgrading DiskSuite to version 4.2, and restoring meta device configurations. Bourne shell scripts that automate the procedure are available for the Solaris 7 and 8 operating environments.

Relocated CDE From the Solaris 2.5.1 Operating Environment Orphaned by an Upgrade to the Solaris 8 Operating Envi ronment (4260819)

This problem affects systems running the Solaris 2.5.1 and the Solaris 2.5.1 unbundled CDE operating environments. However, these systems are only affected if the unbundled CDE has been relocated to a directory other than /usr/dt. The CDE relocation on these systems has been accomplished by creating a symbolic link in /usr/dt that points to the relocated CDE.

When you upgrade to the Solaris 8 operating environment, CDE is reinstalled in /usr/dt, and the link to the relocated version is removed. The relocated CDE is not removed and is therefore orphaned.

If the upgrade involves the reallocation of file systems, the upgrade may fail because the reallocation mechanism does not account for the extra space needed in /usr/dt for the new version of CDE. This failure is not visible until the upgrade has been completed. If this failure occurs, the upgrade log includes a number of messages indicating that more space is needed for an upgrade.

Workaround: Uninstall the relocated CDE before you start upgrading to the Solaris 8 operating environment. You can uninstall by using the install-cde script from the Solaris 2.5.1 CDE CD. You should run this script with the -uninstall flag to remove CDE.

Upgrading the Solaris 7 Operating Environment With Web-Based Enterprise Management (WBEM) 1.0 to the Solaris 8 Operating Environment Causes WBEM 2.0 Not to Work (4274920)

If you installed WBEM 1.0 from the Solaris Easy Access Server (SEAS) 3.0 CD on a system running the Solaris 7 operating environment, you must remove the WBEM 1.0 packages before upgrading to the Solaris 8 operating environment. The Solaris WBEM Services 2.0 do not start after upgrading the Solaris 7 operating environment with WBEM 1.0 to the Solaris 8 operating environment. The Common Information Model (CIM) Object Manager fails to start. The following error message is displayed. 


File not found: /opt/sadm/lib/wbem/cimom.jar

Workaround: Use the pkgrm command to remove the WBEM 1.0 packages before upgrading to the Solaris 8 operating environment.

  1. Use the pkginfo command to check if the WBEM 1.0 packages are installed by typing:


    % pkginfo | grep WBEM

  2. Become superuser.

  3. Use the pkgrm command to remove all WBEM 1.0 packages by typing:


    # pkgrm SUNWwbapi
# pkgrm SUNWwbcor
# pkgrm SUNWwbdev
# pkgrm SUNWwbdoc
# pkgrm SUNWwbm

SUNWeeudt Partially Fails to Install During an Upgrade (4304305)

The upgrade log may state that the SUNWeeudt package was only partially installed.


     Doing pkgadd of SUNWeeudt to /.
     ERROR: attribute verification of 
     </a/usr/dt/appconfig/types/ru_RU.KOI8-R/datatypes.dt> 
     failed pathname does not exist ...

     Installation of <SUNWeeudt> partially failed.
     pkgadd return code = 2

Workaround: Perform the following steps after the upgrade has been completed.

  1. Remove the SUNWeeudt package by typing:


    # pkgrm SUNWeeudt

  2. Add the SUNWeeudt package by typing:


    # pkgadd SUNWeeudt