Installation Bugs That Occur During an Upgrade

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

DiskSuite May Cause Data Loss (4121281)

The DiskSuite^TM 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.

Obsolete Files in SUNWpmi and SUNWxwpls Are Not Removed When Upgrading From the Solaris 7 11/99 Operating Environment to the Solaris 8 Operating Environment (4313654)

When upgrading to the Solaris 8 operating environment, obsolete files in SUNWpmi or SUNWxwpls may not be removed. In addition, the permissions for the /usr/openwin/server/etc/OWconfig file are different in the Solaris 8 operating environment than in past Solaris releases.

The presence of these obsolete files and the difference in file permissions for OWconfig do not cause problems on your upgraded system.

Workaround: Ignore the error messages that list obsolete SUNWpmi or SUNWxpls files that were not removed during the upgrade. Ignore the error messages indicating that the file permissions of /usr/openwin/server/etc/OWconfig are different from what was expected.

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