Upgrade Issues and Bugs

This section describes upgrade bugs. Some bugs might occur while you are upgrading to the Oracle Solaris 10 OS. Other bugs might occur after you have completed the upgrade.

shutdown Command Might Cause the System to Hang After an Upgrade (6751843)

The shutdown command might cause the system to hang after it is upgraded to the Solaris 10 10/09 release. The hang occurs while the svc.startd daemon halts system services.

The Sun Java Web Console debug log file at /var/log/webconsole/console/console_debug_log displays if the web console service is cycling, starting and stopping.

Workaround: Type the following commands:

/usr/share/webconsole/private/bin/wcremove -i console svcadm clear system/webconsole:console smcwebserver start

lucreate and lumake Commands Fail to Create a Copy of a Non-Global Zone That Is Not in the Running State (6659451)

When the lucreate and lumake commands are used on non-global zones that are not in the running state, the commands might not execute successfully. The contents of the original non-global zone and the copy might differ. You might be unable to log in to the zone's consoleby using the zlogin command. The following error message is displayed while you use the zlogin command:

zlogin: makeutx failed

The diagnostic output of the lucreate and lumake commands does not display any errors.

Workaround: Make sure that all non-global zones are in the running state before using the lucreate and lumake commands.

SPARC: Upgrading With Oracle Solaris Live Upgrade From Solaris 8 and Solaris 9 Releases Fails (6638175)

When you use Oracle Solaris Live Upgrade to upgrade to the Solaris 10 10/09 release from a Solaris 8 or Solaris 9 release, the upgrade fails. The installation images compression file is now unzipped by using the 7za utility. The SUNWp7zip package is not included in the Solaris 8 and 9 releases. As a result, Oracle Solaris Live Upgrade fails.

Workaround: To use Oracle Solaris Live Upgrade to upgrade your system to a Solaris 10 10/09 release from a Solaris 8 or a Solaris 9 release, perform the steps listed under Oracle Solaris Live Upgrade Restrictions.

Issues With a DSR Upgrade With Zones (6616788)

A disk space reallocation (DSR) upgrade with zones fails if any zones are installed in the /opt directory. The upgrade might fail during the restoration of the DSR archive. In some cases, the upgrade might be successful, but the system cannot be rebooted.

Workaround: Make sure that the root file system is not 100 percent full before the upgrade. If necessary, remove some files before the upgrade so that the root slice is less than 90 percent full.

Trusted Extensions Upgrade Issues (6616585)

When you upgrade Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the Solaris 10 10/08, Solaris 10 5/09, or Solaris 10 10/09 release, unwanted localized Trusted Extensions packages are installed on your system. This bug occurs because the Trusted Extensions installer in the Solaris 10 11/06 and Solaris 10 8/07 releases installs localized packages by default. No error message is displayed.

Workaround: Before upgrading Trusted Extensions to the current release, remove the following localized Trusted Extensions packages.

System Cannot Communicate With ypbind After an Upgrade (6488549)

This bug occurs during an upgrade from the Solaris 10 Hardware 2 (HW2) release to the current Solaris 10 10/09 release.

In the Solaris 10 HW2 release, the name_service.xml file for any name service, such as NIS, NIS+, FILES, or LDAP is as follows:

# ls -l name_service.xml
lrwxrwxrwx   1 root     root     10 Apr 10 16:26 name_service.xml -> ns_files.xml

If the name service is NIS, the name_service.xml file links to ns_files.xml. However, the contents of the ns_files.xml file are the same as ns_nis.xml.

  # cat /etc/release
                     Solaris 10 3/05 HW2 s10s_hw2wos_05 SPARC
           Copyright 2005 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 26 September 2005
  # cd /var/svc/profile
  # ls -l name_service.xml ns_files.xml ns_nis.xml
  lrwxrwxrwx   1 root   other    12 May 21 04:06 name_service.xml -> ns_files.xml
  -r--r--r--   1 root   sys     779 May 21 04:25 ns_files.xml
  -r--r--r--   1 root   sys     779 Jan 21  2005 ns_nis.xml
  #
  # diff ns_files.xml ns_nis.xml
  # diff name_service.xml ns_nis.xml

In the preceding output, the ns_nis.xml and ns_files.xml files are the same. This means that the name_service.xml file symbolically links to the wrong name service file. The name_service.xml file links to ns_files.xml. Instead, the name_service.xml file should link to the ns_nis.xml.

After an upgrade from Solaris 10 Hardware 2 to the current Solaris 10 10/09 release, the following message is displayed on the console or logged in the messages file:

Oct 23 12:18:45 vt2000a automount[301]: [ID 366266 daemon.error] 
can't read nis map auto_master: can't communicate with ypbind - retrying 

Also, the /network/nis/client:default service is offline.

Workaround: Choose one of the following workarounds:

• Workaround 1: Before an upgrade, remove the /var/svc/profile/name_service.xml file.

• Workaround 2: After an upgrade, change the /var/svc/profile/name_service.xml link to the correct ns_<xxx>.xml file, based on the name service.

Upgrade Fails on Systems With Zones That Have Been Installed but Not Booted

A non-global zone that has been installed but never booted or made ready prevents a system from being upgraded correctly. No error message is displayed.

Workaround: If such a zone is found, the zone should be made ready and then halted prior to starting the upgrade. For example:

global# zoneadm -z myzone ready ; zoneadm -z myzone halt

Upgrading an Oracle Solaris 10 System With Non-Global Zones to the Solaris 10 10/09 Release Might Cause the Local File System Service to Fail (6428258)

Upgrading a Solaris 10 3/05 or Solaris 10 1/06 system with non-global zones to the Solaris 10 10/09 release might cause the SMF service that mounts local file systems to fail in the non-global zones. As a result, other services in the non-global zones might fail to start.

After upgrading an Oracle Solaris 10 system with non-global zones to the Solaris 10 10/09 release, services might be in the maintenance state. For example:

# zlogin myzone svcs -x
    svc:/system/filesystem/local:default (local file system mounts)
     State: maintenance since Wed May 24 13:18:06 2006
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
       See: http://sun.com/msg/SMF-8000-KS
       See: /var/svc/log/system-filesystem-local:default.log
    Impact: 18 dependent services are not running.  (Use -v for list.)

Workaround:

Reboot the non-global zone from the global zone. For example:

global# zoneadm -z myzone reboot

Device ID Discrepancies After an Upgrade From the Solaris 9 9/04 OS

In this Oracle Solaris release, Solaris Volume Manager displays device ID output in a new format. The Solaris 9 9/04 OS, which introduced device ID support in disk sets, does not recognize the new format. When you upgrade to the Oracle Solaris 10 OS from the Solaris 9 9/04 release, device IDs that are associated with existing disk sets are not updated in the Solaris Volume Manager configuration. If you need to revert to the Solaris 9 9/04 OS, configuration changes made to disk sets after the upgrade might not be available to the Solaris 9 9/04 OS. For more information, see Chapter 25, Troubleshooting Solaris Volume Manager (Tasks), in Solaris Volume Manager Administration Guide.

Obsolete Uninstallers Not Removed When Oracle Solaris Live Upgrade Is Used to Upgrade From Previous Releases (6198380)

If you use Oracle Solaris Live Upgrade to upgrade from a Solaris 8 or Solaris 9 release to the Oracle Solaris 10 OS, obsolete uninstaller programs are not removed. These uninstaller programs from previous releases remain in the system's /var/sadm/prod directory.

The following obsolete uninstallers are not removed:

uninstall_Alternate_Pathing_2_3_1.class
uninstall_CDRW_1_1.class o uninstall_CDRW_1_0.class
uninstall_Bonus_Localization_-_Catalan_CDE_Desktop.class
uninstall_Bonus_Localization_-_Polish_CDE_Desktop.class
uninstall_Bonus_Localizations_-_Russian_CDE_Desktop.class
uninstall_Capacity_on_Demand_1_0.class
uninstall_Java3D_1_3_1.class
uninstall_Java3D_1_3.class
uninstall_Java3D_1_2_1_04.class
uninstall_Java3D_1_2_1_03.class
uninstall_Lights_Out_Management_2_0.class
uninstall_Man_Page_Supplement.class
uninstall_OpenGL_1_3.class
uninstall_OpenGL_1_2_3.class
uninstall_Netra_ct_Platform_1_0.class
uninstall_Netra_t11xx_Alarms_2_0.class
uninstall_Netscape_6_2_3.class
uninstall_Netscape_6_2_1_Beta.class
uninstall_PC_launcher_1_0_2.class
uninstall_PC_launcher_1_0_1_PCfileviewer_1_0_1.class
uninstall_RSC_2_2_2.class
uninstall_RSC_2_2_1.class
uninstall_RSC_2_2.class
uninstall_ShowMeTV_1_3.class
uninstall_Solaris_9_French_Localization.class
uninstall_Solaris_9_German_Localization.class
uninstall_Solaris_9_Hong_Kong_Traditional_Chinese_Localization.class
uninstall_Solaris_9_Italian_Localization.class
uninstall_Solaris_9_Japanese_Localization.class
uninstall_Solaris_9_Korean_Localization.class
uninstall_Solaris_9_Simplified_Chinese_Localization.class
uninstall_Solaris_9_Spanish_Localization.class
uninstall_Solaris_9_Swedish_Localization.class
uninstall_Solaris_9_Traditional_Chinese_Localization.class
uninstall_Solaris_On_Sun_Hardware_Documentation.class
uninstall_Sun_Hardware_AnswerBook.class
uninstall_SunATM_5_0.class
uninstall_SunATM_5_1.class
uninstall_SunFDDI_PCI_3_0.class
uninstall_SunFDDI_SBus_7_0.class
uninstall_Sun_Fire_880_FC-AL_Backplane_Firmware_1_0.class
uninstall_Sun_Fire_B10n_Load_Balancing_Blade_1_1.class
uninstall_SunForum_3_1.class
uninstall_SunForum_3_2.class
uninstall_SunHSI_PCI_3_0.class
uninstall_SunHSI_SBus_3_0.class
uninstall_SunScreen_3_2.class
uninstall_SunVTS_5_1_PS6.class
uninstall_SunVTS_5_1_PS5.class
uninstall_SunVTS_5_1_PS4.class
uninstall_SunVTS_5_1_PS3.class
uninstall_SunVTS_5_1_PS2.class
uninstall_SunVTS_5_1_PS1.class
uninstall_SunVTS_5_0.class
uninstall_System_Management_Services_1_4.class
uninstall_System_Management_Services_1_3.class
uninstall_System_Management_Services_1_2.class
uninstall_System_Service_Processor_3_5.class
uninstall_WBEM_DR_1_0.class
uninstall_Web_Start_Wizards_SDK_3_0_2.class
uninstall_Web_Start_Wizards_SDK_3_0_1.class
uninstall_Web_Start_Wizards_SDK.class
uninstall_XML_Libraries_2_4_12.class

Workaround: After you upgrade the system, manually remove the obsolete uninstallers in the /var/sadm/prod directory.

Additional Related Locales Might Be Installed

When you select a locale for your installation, additional related locales might also be installed. This change in behavior occurs in the Oracle Solaris 10 release because all full locales, with message translations, and the Asian and Japanese partial locales, locale enabler, have been repackaged based on language support for locales. Other partial locales are still packaged and installed based on geographic region, such as Central Europe.