Sun and OracleChannel SunHow to BuyLog In繁體中文

Solaris 9 4/03 Release Notes
只搜尋這本書
搜尋說明
查看這本書:
包含在
尋找其他文件
熱門支援資源
 以 PDF 格式下載這本書 (699 KB)

Chapter 1 Installation Issues

This chapter describes problems that relate to the installation of the Solaris 9 4/03 operating environment.

The following installation bug descriptions have been added to this chapter since this document was published on the Solaris 9 4/03 Documentation CD and in the Installation Kiosk on the Solaris 9 4/03 Installation CD.

Issues You Need to Know About Before Installing Solaris 9 4/03 Software

SPARC: Booting From the Solaris 9 4/03 DVD

The Solaris 9 4/03 operating environment is now available on DVD. To install or upgrade from DVD, insert the Solaris 9 4/03 DVD into the DVD-ROM drive and boot the system from the ok prompt with the following command. 


ok boot cdrom

x86: Solaris 9 4/03 Installation CD Partition Issue

If the Solaris Web Start 3.0 program on the Solaris 9 4/03 Installation CD is unable to locate a Solaris fdisk partition on a system, you must create a Solaris fdisk partition on your root disk.

Caution – Caution –

If you change the size of an existing fdisk partition, all data on that partition is automatically deleted. Back up your data before you create a Solaris fdisk partition.

The Solaris Web Start 3.0 program requires two fdisk partitions to perform an installation.

  • Solaris fdisk partition

    This is the typical Solaris fdisk partition.

  • x86 boot fdisk partition

    This is a 10–Mbyte fdisk partition that enables x86-based systems to boot the miniroot that is placed on the newly created swap slice. The swap slice is located on the Solaris fdisk partition.

Note –

The installation program on the Solaris 9 4/03 Installation CD creates the x86 boot partition, removing 10 Mbytes from the Solaris fdisk partition. This removal prevents any existing fdisk partitions from being altered.

This partition should not be created manually.

This requirement also prevents you from using the Solaris 9 4/03 Installation CD to upgrade from the Solaris 2.6 or Solaris 7 releases to the Solaris 9 4/03 operating environment. For more information, refer to Upgrade Issues.

x86: Change in Default Boot-Disk Partition Layout

In the Solaris 9 4/03 operating environment, the Solaris Web Start and suninstall installation programs use, by default, a new boot-disk partition layout to accommodate the Service partition on SunTM LX50 systems. This installation program enables you to preserve an existing Service partition.

The new default includes the following partitions:

  • First partition – Service partition (existing size on system)

  • Second partition – x86 boot partition (approximately 11 Mbytes)

  • Third partition – Solaris partition (remaining space on the boot disk)

If you want to use this default layout, select Default when the Solaris Web Start or suninstall program asks you to choose a boot-disk layout.

Note –

If you install the Solaris 9 4/03 (x86 Platform Edition) operating environment on a system that does not currently include a Service partition, the Solaris Web Start and suninstall programs do not create a new Service partition by default. If you want to create a Service partition on your system, see x86: Service Partition Not Created by Default on Systems With No Existing Service Partition.

You can also choose to manually edit the disk partition layout by using the fdisk utility. You might want to manually edit the boot-disk partitions under the following conditions:

  • You want to preserve an existing Sun Linux partition on the system.

  • You need to create a Solaris partition, but want to preserve other existing partitions on the disk.

Note –

If your system contains an upgradable version of the Solaris operating environment, but does not contain an x86 boot partition, you might not be able to upgrade by using the Solaris Installation CD. To upgrade a system with no x86 boot partition to the Solaris 9 4/03 operating environment, use the suninstall installation program on the Solaris 9 4/03 Software 1 of 2 CD.

SPARC: Default Solaris JumpStart Profile Might Not Install Multiple Locales on Small Disks

If you use the default Solaris JumpStartTM profile on the Solaris 9 4/03 media to install multiple locales on a system with a small disk, the installation might fail. This problem might occur under the following conditions.

  • You use the default Solaris JumpStart profile to install any locale other than the C locale on a system with a 2.1-Gbyte disk.

  • You use the default Solaris JumpStart profile to install two or more locales on a system with a 4-Gbyte disk.

x86: Service Partition Not Created by Default on Systems With No Existing Service Partition

If you install the Solaris 9 4/03 operating environment on a system that does not currently include a Service partition, the installation program might not create a Service partition by default. If you are including a Service partition on the same disk as the Solaris partition, you must re-create the Service partition before you install the operating environment.

If you installed the Solaris 8 2/02 operating environment on a Sun LX50 system, the installation program might not have preserved the Service partition. If you did not manually edit the fdisk boot-partition layout to preserve the Service partition, the installation program deleted the Service partition during the installation.

Note –

If you did not specifically preserve the Service partition when you installed the Solaris 8 2/02 operating environment, you cannot re-create the Service partition and upgrade to the Solaris 9 4/03 operating environment. You must perform an initial installation of the software.

Workaround: If you are including a Service partition on the disk that contains the Solaris partition, choose one of the following workarounds.

  • To use the Solaris Web Start installation program to install from the Solaris 9 4/03 Installation CD, follow these steps.

    1. Delete the contents of the disk.

    2. Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.

      For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.

    3. Insert the Solaris 9 4/03 Installation CD in the CD-ROM drive.

    4. Begin the installation.

      When the installation program detects the Service partition, the following message is displayed:


      The default layout for the bootdisk is one x86 Boot partition
and a Solaris partition on the remaining space. The Service fdisk
partition, if one exists, is also preserved by default.

Select one of the following to continue:

1) Use the default layout
2) Run fdisk to manually edit the disk
3) Exit

Please make a selection: [?]

    5. Type 1 to use the default layout.

      The installation program preserves the Service partition and creates the x86 boot partition and the Solaris partition.

      Note –

      The Solaris Web Start installation program creates the x86 boot partition by removing 10 Mbytes from the Solaris fdisk partition. This utility prevents any existing fdisk partitions from being altered. Do not create this partition manually.

    6. Complete the installation.

  • To install from a network installation image or from the Solaris 9 4/03 DVD over the network, follow these steps.

    1. Delete the contents of the disk.

    2. Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.

      For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.

    3. Boot the system from the network.

      The Customize fdisk Partitions screen is displayed.

    4. To load the default boot-disk partition layout, click Default.

      The installation program preserves the Service partition and creates the x86 boot partition and the Solaris partition.

      For more information on booting from the network, see the Solaris 9 Installation Guide.

  • To use the suninstall program to install from the Solaris 9 4/03 Software 1 of 2 CD or from a network installation image on a boot server, follow these steps.

    1. Delete the contents of the disk.

    2. Before you install, create the Service partition by using the Sun LX50 Diagnostics CD.

      For information on how to create the Service partition, see the Sun LX50 Server User's Manual and the Sun LX50 Knowledge Base at http://cobalt-knowledge.sun.com.

    3. Boot the system.

      The installation program prompts you to choose a method for creating the Solaris partition.

    4. Select the Use rest of disk for Solaris partition option.

      The installation program preserves the Service partition and creates the Solaris partition.

    5. Complete the installation.

      For more information on booting from the network, see the Solaris 9 Installation Guide.

x86: Solaris Device Configuration Assistant Boot Diskette Is Not Available

The Solaris 9 Device Configuration Assistant is not delivered as a boot diskette in the Solaris 9 4/03 release. To boot the Device Configuration Assistant, choose one of the following options.

  • If your system's BIOS supports CD booting, boot from the Solaris 9 4/03 (x86 Platform Edition) Installation CD, the Solaris 9 4/03 Software (x86 Platform Edition) 1 of 2 CD, or the Solaris 9 4/03 Software (x86 Platform Edition) DVD.

  • Create a boot diskette by copying the boot-diskette image to a diskette. The boot-diskette image is available at the following locations.

    Copy the image to a diskette, then boot the system from the diskette.

  • If your system supports Preboot Execution Environment (PXE) booting and an install image is available on the network, boot from the network.

    Enable the system to use PXE by using the system's BIOS setup tool or the network adapter's configuration setup tool.

For more information, see the Solaris 9 Installation Guide.

x86: Update the DPT PM2144UW Controller BIOS to the Latest Revision Before Upgrading to the Solaris 9 4/03 Operating Environment

The Solaris 9 4/03 operating environment includes a feature that enables you to install large partitions. The DPT PM2144UW controller's BIOS must support logical block addressing (LBA). The latest revision of the BIOS fully supports LBA access. You might need to update other DPT controller models to support LBA.

Workaround: Prior to upgrading your system to the Solaris 9 4/03 operating environment, ensure that the DPT PM2144UW controller's BIOS is the latest available version from DPT.

To determine if your system has a DPT controller, perform the following steps:

  1. Run the prtconf -D.

  2. If the name dpt is displayed, run the card's configuration utility to obtain information about the model and BIOS revision.

  3. Upgrade DPT PM2144UW controllers by flashing the BIOS or by installing the latest BIOS EPROM that you have obtained from DPT. See http://www.dpt.com for the latest BIOS images for all DPT controllers.

You can now upgrade the system.

x86: Do Not Upgrade Hewlett-Packard (HP) Vectra XU Series Systems With BIOS Version GG.06.13

The Solaris 9 4/03 operating environment includes a feature that enables you to install large partitions. The system BIOS must support logical block addressing (LBA). BIOS Version GG.06.13 does not support LBA access. The Solaris boot programs cannot manage this conflict. This issue can also affect other HP Vectra systems.

If you perform this upgrade, your HP system can no longer boot. Only a blank black screen with a flashing underscore cursor is displayed.

Workaround: Do not upgrade HP Vectra XU Series systems with the latest BIOS Version GG.06.13 to the Solaris 9 4/03 operating environment because it no longer supports these systems.

You can still boot your system by using the boot diskette or boot CD because the boot paths do not use the hard disk code. Then select the hard disk as your bootable device instead of the network or CD-ROM drive.

Bugs You Need to Know About Before Installing Solaris 9 4/03 Software

x86: suninstall Exits When Choosing to Save Service Partition and Create Solaris Partition (4832216)

If you use the suninstall installation program to install the Solaris 9 4/03 (x86 Platform Edition) operating environment on a system with an existing service partition, the installation program might exit. This problem occurs under the following conditions:

  • You use the suninstall program to install the Solaris 9 4/03 operating environment.

  • During the installation, you choose to lay out a disk with an existing service partition, but no Solaris fdisk partition.

  • On the Create Solaris fdisk Partition panel, you choose the Save service partition, create Solaris fdisk partition option.

Workaround: Choose one of the following workarounds.

  • To manually create a Solaris fdisk partition during the suninstall program, follow these steps:

    1. When the suninstall installation program asks you to choose a method to create the Solaris fdisk partition, choose the Manually create fdisk partitions option.

    2. Preserve the service partition and create the Solaris fdisk partition.

    3. Complete the installation.

  • To manually create a Solaris fdisk partition by using the fdisk command, follow these steps:

    1. Exit from the suninstall installation program by pressing the F5 function key.

    2. Open a terminal window.

      See the fdisk(1M) man page for more information on creating fdisk partitions.

    3. Restart the suninstall installation program by typing the following command:


      # suninstall

    4. Complete the installation.

x86: Installations Might Fail on Systems With 3Com 3c905C Network Interface Cards (4791458)

If you perform a network installation on a system with a 3Com 3c905C network interface card, the following error message might be displayed:


elxl%d: no active connection found; please connect

After this error message is displayed, the installation might continue, or the installation might hang.

Workaround: Choose one of the following workarounds.

  • Use a different network interface to perform the network installation.

  • Use the Solaris 9 4/03 DVD or CD media to install the system.

For more information on how to perform an installation from the network, see the Solaris 9 Installation Guide.

x86: PXE Network Boot Does Not Execute Successfully on Sun LX50 Systems (4725108)

If you use the Preboot Execution Environment (PXE) network boot to install the Solaris 9 4/03 operating environment on a SunTM LX50 system, the network boot might fail. The following message is displayed:


error: Assertion failure: - "rp->flags & RESF_ALT", "ur.c" line 80

The root filesystem is not mounted and the configuration assistant
has exited prematurely. Booting is unlikely to succeed. 
CTL-ALT-DEL may be used to reset the machine.

Failover to boot interpreter - type ctrl-d to resume boot

Workaround: Choose one of the following workarounds.

  • If you do not need to use PXE network boot, follow these steps.

    1. Boot the system by using one of the following media.

      • Solaris 9 4/03 Installation CD

      • Solaris 9 4/03 Software 1 of 2 CD

      • Solaris Device Configuration Assistant (DCA) on a boot diskette

        See the Solaris 9 Installation Guide for more information on booting from the Solaris DCA.

    2. When the DCA prompts you to choose a network device, select the appropriate network device to use to boot the system.

  • If you want to use PXE network boot, disable the serial console in the system's BIOS during the installation. For instructions on how to modify the BIOS on Sun LX50 systems, see the Sun LX50 Server Manual at http://www.sun.com/servers/entry/lx50/documentation2.html.

Boot From Solaris DVD Fails on Systems With Toshiba SD-M1401 DVD-ROM (4467424)

If your system has a Toshiba SD-M1401 DVD-ROM drive with firmware revision 1007, the system cannot boot from the Solaris 9 4/03 DVD.

Workaround: Apply patch 111649–03, or later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. Patch 111649–03 is included on the Solaris 9 4/03 Supplement CD in the following directory.


DVD_Firmware/Patches

See the README file in this directory for instructions on how to install the patch. Be sure to read and follow all the cautions and warnings in this README file before you install the patch.

Cannot Access Data on Solaris 9 4/03 DVD in Solaris 2.6 and Solaris 7 Operating Environments (4511090)

If your system is running the Solaris 2.6 or Solaris 7 operating environment, Volume Management incorrectly mounts the Solaris 9 4/03 DVD. The DVD can be mounted, but the data is inaccessible. As a result, you cannot set up an install server, perform a Live Upgrade, or access any data on the media.

Workaround: Choose one of the following workarounds.

  • Apply the patches appropriate for your system.

    Table 1–1 DVD Patches for the Solaris 2.6 and Solaris 7 Operating Environments

    Release

    Patch ID

    Solaris 2.6 operating environment

    107618-03

    Solaris 7 operating environment

    107259-03

    Solaris 2.6 operating environment

    107619-03

    Solaris 7 operating environment

    107260-03

  • Manually mount the Solaris 9 4/03 DVD. Do not use Volume Management to mount the DVD. Follow these steps.

    1. Become superuser.

    2. Stop Volume Management.


      # /etc/init.d/volmgt stop

    3. Manually mount the DVD.


      # mkdir /mnt1
# mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /mnt1

    4. Verify that the DVD is mounted and the data is accessible.


      # cd /mnt1
# ls

      The system returns the following information if the DVD is correctly mounted.


      Copyright  Solaris_9

Installation Bugs

SPARC: Systems With Multiple Interfaces Recognize All Interfaces as Usable After Installation or Upgrade (4640568)

If you install or upgrade to the Solaris 9 4/03 operating environment on a system with multiple network interfaces, the system recognizes all system interfaces as usable. Interfaces that are not plugged in to the network or that are not intended for use appear in the output of the ifconfig -a command. Additionally, interfaces with identical Ethernet addresses might be assigned identical IP addresses. The following error message is displayed.


ifconfig: setifflags: SIOCSLIFFLAGS: qfe3: Cannot assign requested address

This problem also occurs on systems that have the local-mac-address PROM variable set to false. The problem occurs because all interfaces are configured with the same IP address.

Workaround: Choose one of the following workarounds.

  • To plumb only the configured interface, reboot the system after the initial boot.

  • To assign a different IP address to each network interface, set the local-mac-address PROM variable to true in one of the following ways.

    • At the ok prompt, type the following command.


      ok setenv local-mac-address? true

    • In a terminal window, type the following command as superuser.


      # eeprom local-mac-address?=true

Installation Bugs That Occur During an Installation From Solaris 9 4/03 Software 1 of 2 CD

Warnings Might Occur When a File System Is Created (4189127)

When a file system is created during installation, one of the following warning messages might be displayed. 


Warning: inode blocks/cyl group (87) >= data blocks (63) in last
cylinder group. This implies 1008 sector(s) cannot be allocated.

Or:


Warning: 1 sector(s) in last cylinder unallocated

The warning occurs when the size of the file system that you created does not equal the space on the disk that is being used. This discrepancy can result in unused space on the disk that is not incorporated into the indicated file system. This unused space is not available for use by other file systems.

Workaround: Ignore the warning message.

Bug That Occurs During an Installation or an Upgrade

Invalid Error Message Encountered When Installing Solaris WBEM Providers Package SUNWwbpro (4824518)

When you install the Solaris 9 4/03 operating environment, the following error message is recorded in the /var/sadm/system/logs/install_log file:


/tmp/Solaris_Application.mof: No such file or directory

If you upgrade to the Solaris 9 4/03 operating environment, the same error message is recorded in the /var/sadm/system/logs/upgrade_log file.

The message is encountered during the installation of the Solaris WBEM Providers Package (SUNWwbpro).

Workaround: Ignore the error message. This message does not affect the installation of the package. The error occurs because the installation program attempts to delete a temporary file that does not exist.

Upgrade Issues

Cannot Access Storage Area Networks Through SUNWsan With Solaris 9 4/03 Operating Environment

If your Solaris 8 system is connected to storage area networks (SANs), check with your support engineer before you upgrade to the Solaris 9 4/03 operating environment. Solaris 8 systems with the SUNWsan package installed might require special procedures to upgrade to the Solaris 9 4/03 operating environment. To find out if the SUNWsan package is installed on the system, type the following command in a terminal window.


# pkginfo SUNWsan

If the SUNWsan package is installed, the following information is displayed.


	system      SUNWsan       SAN Foundation Kit

x86: Cannot Use Solaris 9 4/03 (x86 Platform Edition) Installation CD to Upgrade x86 Systems to the Solaris 9 4/03 Operating Environment

You cannot use Solaris 9 4/03 (x86 Platform Edition) Installation CD to upgrade x86-based systems from the Solaris 2.6 or Solaris 7 operating environment to the Solaris 9 4/03 operating environment because of the x86 boot-partition requirement. Use the Solaris 9 4/03 Software (x86 Platform Edition) 1 of 2 CD to upgrade from the Solaris 2.6 or Solaris 7 operating environment to the Solaris 9 4/03 operating environment on x86-based systems.

Solaris Management Console 2.1 Software Is Not Compatible With Solaris Management Console 1.0, 1.0.1, or 1.0.2 Software

Solaris Management Console 2.1 software is not compatible with Solaris Management Console 1.0, 1.0.1, or 1.0.2 software. If you are upgrading to the Solaris 9 4/03 operating environment, and you have Solaris Management Console 1.0, 1.0.1, or 1.0.2 software installed, you must first uninstall the Solaris Management Console software before you upgrade. Solaris Management Console software might exist on your system if you installed the SEAS 2.0 overbox, the SEAS 3.0 overbox, or the Solaris 8 Admin Pack.

Workaround: Choose one of the following workarounds.

  • Before you upgrade, use the /usr/bin/prodreg command to perform a full uninstall of Solaris Management Console software.

  • If you did not uninstall Solaris Management Console 1.0, 1.0.1, or 1.0.2 software before you upgraded to the Solaris 9 4/03 operating environment, you must first remove all Solaris Management Console 1.0, 1.0.1, or 1.0.2 packages. Use the pkgrm command for package removal instead of the prodreg command. Carefully follow the order of package removal. Complete the following steps.

    1. Become superuser.

    2. Type the following command.


      # pkginfo | grep “Solaris Management Console“

      If the description does not start with “Solaris Management Console 2.1,” the package names in the output identify a Solaris Management Console 1.0 package.

    3. Use the pkgrm command to remove all instances of Solaris Management Console 1.0 packages in the following order.

      Note –

      Do not remove any package that has “Solaris Management Console 2.1” in its description. For example, SUNWmc.2 might indicate Solaris Management Console 2.1 software.

      If the pkginfo output displays multiple versions of Solaris Management Console 1.0 packages, use the pkgrm command to remove both packages. Remove the original package and then remove the package that has been appended with a number. For example, if the SUNWmcman and SUNWmcman.2 packages appear in the pkginfo output, first remove the SUNWmcman package and then remove the SUNWmcman.2 package. Do not use the prodreg command.


      # pkgrm SUNWmcman
# pkgrm SUNWmcapp
# pkgrm SUNWmcsvr
# pkgrm SUNWmcsvu
# pkgrm SUNWmc
# pkgrm SUNWmcc
# pkgrm SUNWmcsws

    4. In a terminal window, type the following command.


      # rm -rf /var/sadm/pkg/SUNWmcapp

    The Solaris Management Console 2.1 software should now function properly. For future maintenance, or if the Solaris Management Console 2.1 software does not function properly, remove the Solaris Management Console 2.1 software. Reinstall the software by completing the following steps.

    1. Use the pkgrm command to remove all Solaris Management Console 2.1 packages and dependent packages in the following order.

      Note –

      If your installation has multiple instances of Solaris Management Console 2.1 packages, such as SUNWmc and SUNWmc.2, first remove SUNWmc, and then SUNWmc.2. Do not use the prodreg command.


      # pkgrm SUNWpmgr
# pkgrm SUNWrmui
# pkgrm SUNWlvmg
# pkgrm SUNWlvma
# pkgrm SUNWlvmr
# pkgrm SUNWdclnt
# pkgrm SUNWmga
# pkgrm SUNWmgapp
# pkgrm SUNWmcdev
# pkgrm SUNWmcex
# pkgrm SUNWwbmc
# pkgrm SUNWmc
# pkgrm SUNWmcc
# pkgrm SUNWmccom

    2. Insert the Solaris 9 4/03 Software 1 of 2 CD into your CD-ROM drive. Type the following in a terminal window.


      # cd /cdrom/sol_9_403_sparcia/s0/Solaris_9/Product
# pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev \
  SUNWmgapp SUNWmga SUNWdclnt SUNWlvmr SUNWlvma SUNWlvmg SUNWpmgr \
  SUNWrmui

    All previous Solaris Management Console versions are removed. The Solaris Management Console 2.1 software is now functional.

Installation Bugs That Occur During an Upgrade

Upgrade Fails to Install SUNWceudt Package (4826785)

If you upgrade from the Solaris 9, Solaris 9 9/02, or Solaris 9 12/02 operating environment to the Solaris 9 4/03 release, the following errors occur when you use the pkgchk command with the -n option:


ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/datatypes.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/develop.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtfile.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtmail.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtpad.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/print.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/uxstd.dt
pathname does not exist

Workaround: Use the Solaris 9 4/03 DVD or the Solaris 9 4/03 Software 1 of 2 CD to add back the SUNWceudt package. Follow these steps:

  1. Become superuser.

  2. Remove the SUNWceudt package.


    # pkgrm SUNWceudt

  3. Change directories to the product directory.


    # cd path-to-Solaris-9/Product

  4. Add the SUNWceudt package.


    # pkgadd   -d `pwd` SUNWceudt

Manually Register VDiskMgr.jar File Delivered by Patch 114711-01 or 114712-01 After Upgrading (4818306)

If you applied on your system patch 114711-01 (SPARC Platform Edition), or patch 114712-01 (x86 Platform Edition) , you must manually register the VDiskMgr.jar file delivered with these patches after you upgrade to the Solaris 9 4/03 operating environment. If you do not manually register the VDiskMgr.jar file that is delivered with the patch, the existing VDiskMgr.jar file remains on your system. In addition, the patch does not fully fix the problem.

To determine if either of these patches is installed on your system, type one of the following commands:

  • SPARC systems:


    # patchadd -p | grep '114711-01'

  • x86 systems:


    # patchadd -p | grep '114712-01'

Workaround: Manually register the VDiskMgr.jar file delivered with the two specified patches after you upgrade to the Solaris 9 4/03 operating environment. Follow these steps:

  1. Become superuser.

  2. Replace the existing VDiskMgr.jar file with the .jar file delivered with the patch.


     # /usr/sadm/bin/smcregister tool -n \
com.sun.admin.diskmgr/VDiskMgr.jar \
/usr/sadm/lib/diskmgr/VDiskMgr.jar \
/usr/sadm/lib/dismgr/VDiskMgr_classlist.txt \
/usr/sadm/lib/diskmgr/VDiskMgrInfo.xml > /dev/null 2>$1

  3. Replace the existing VDiskMgr in the tools box with the VDiskMgr tool delivered in the patch.


    # /usr/sadm/bin/smcregister toolbox add -f tool \
com.sun.admin.diskmgr.client.VDiskMgr \
-F "/Storage/" >/dev/null 2>&1

  4. Stop the WBEM server.


    # /etc/init.d/init.wbem stop

  5. Restart the WBEM server.


    # /etc/init.d/init.wbem start

SPARC: Solaris Management Console Applications Dependent on Managed Object Format (MOF) Files Might Fail After Upgrade (4825349)

If you upgrade from the Solaris 9 operating environment to the Solaris 9 9/02, Solaris 9 12/02, or Solaris 9 4/03 release, the upgrade does not reregister existing Managed Object Format (MOF) files. During the upgrade, the old /var/sadm/wbem/logr directory is saved as the /var/sadm/wbem/logru3 directory. The registered MOF files are not reregistered after the upgrade. As a result, Solaris Management Console applications that depend on MOF files will fail.

The following error message is displayed when you use the console Mounts and Disks tools:


CIM_ERR_NOT_FOUND

Workaround: Manually register the missing MOF files. The MOF files are available in the /var/sadm/wbem/logru3 directory. Complete the following steps:

  1. Become superuser.

  2. Manually register the MOF files.


     # /usr/sadm/bin/mofreg -r tag mof-file

    where tag is the directory located in the /var/sadm/wbem/logru3/unregDir/ directory and mof–file is the MOF file located in the tag directory.

    For example: 


    # /usr/sadm/bin/mofreg -r svm \
/var/sadm/wbem/logru3/unregDir/svm/svm/Solaris_Vm1.0.mof

  3. Stop the WBEM server.


    # /etc/init.d/init.wbem stop

  4. Restart the WBEM server.


    # /etc/init.d/init.wbem start

Installer Text Display Problem When Using Solaris Live Upgrade (4736488)

When using the Solaris Live Upgrade luupgrade(1M) command with the -i option to complete an upgrade of an inactive boot environment, the text that the installers display might be unreadable in some languages. The text is corrupted when the installers request fonts that do not exist on the older release that is on the current boot environment.

Workaround: Choose one of the following workarounds.

  • Use a combined network installation image to do the install.

  • Enable the C locale by setting the environment variable on your system.

    • If you are using the Bourne shell or Korn shell, follow these steps.

      1. Set the C locale.


         # LANG=C; export LANG

      2. Begin the installation.

    • If you are using the C shell, follow these steps.

      1. Type the following.


        # csh

      2. Set the C locale.


         # setenv LANG C

      3. Begin the installation.

SPARC: luupgrade Command Cannot Add Patches When a Patch List File Is Specified (4679511)

If you use the -s option with the luupgrade command to add patches with a directory and a patch list file, the patches are not added. A message similar to the following message is displayed:


/usr/sbin/luupgrade [52]:		3 patch-list-file: bad number

In the previous message, patch-list-file is the patch list file you specified for the luupgrade command to use to add patches.

Workaround: To add patches that specify a patch list file, perform the following steps.

  1. Become superuser.

  2. Mount the boot environment that you are patching.


    # lumount boot-envir-name mount-point

  3. Add the patches to the boot environment.


    # /usr/sbin/patchadd -R mount-point -M patch-path patch-list-file-name

    In the previous command, patch-path is the path name of a directory that contains patches to add. The patch-list-file-name is the file that contains the list of patches you are adding.

  4. Unmount the boot environment. 


    # luumount boot-envir-name

SPARC: Removal of SUNWjxcft Package Records Error During Upgrade (4525236)

When you upgrade from the Solaris 8 operating environment to the Solaris 9 or the Solaris 9 4/03 operating environment, a problem is encountered when the SUNWjxcft package is removed. The following error message is recorded in the upgrade_log file:


Removing package SUNWjxcft:
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.upr
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.scale
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.alias
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.upr
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.scale
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.alias
Removal of <SUNWjxcft> was successful

Workaround: Ignore the error message.

Upgrading From Solaris 8 Operating Environment Might Create Redundant Kerberos Privacy Mechanisms (4672740)

In the Solaris 9 4/03 operating environment, the Kerberos version 5 global mechanism includes privacy support. Therefore, the Kerberos domestic mechanism is not needed. If you installed the Kerberos domestic mechanism that is located in /usr/lib/gss/do/mech_krb.so.1 on a Solaris 8 system, remove the Kerberos domestic mechanism, then upgrade the system to the Solaris 9 4/03 operating environment.

Workaround: Follow these steps before you upgrade to the Solaris 9 4/03 operating environment.

  1. Type the following command to determine if the Kerberos domestic mechanism is installed on the system.


    % pkginfo | fgrep ' SUNWk5'

    • If the output of this command includes any SUNWk5 package names, the Kerberos domestic mechanism is installed on the system. Go to step 2.

    • If the output does not include any SUNWk5 package names, the Kerberos domestic mechanism is not installed on the system. Skip the rest of these steps. Upgrade the system.

  2. Back up the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.


    % tar -cf /var/tmp/krb_config_files.tar /etc/nfssec.conf /etc/gss/qop

  3. Verify that the files are backed up by typing the following command.


    % tar -tf /var/tmp/krb_config_files.tar

  4. Remove each package that is listed in the output of step 1.


    % pkgrm package-name package-name package-name

  5. Upgrade to the Solaris 9 4/03 operating environment.

    The upgrade program updates the global Kerberos mechanism code and enables Kerberos privacy support.

  6. In a text editor, change the following lines in the /etc/gss/mech file.

    • Uncomment the following line.


      kerberos_v5     1.2.840.113554.1.2.2    gl/mech_krb5.so gl_kmech_krb5

      If necessary, add the previous line to the /etc/gss/mech file.

    • Remove the following line.


      kerberos_v5     1.2.840.113554.1.2.2    do/mech_krb5.so do_kmech_krb5

    • Restore the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.


      % tar -xf /var/tmp/krb_config_files.tar

Upgrading to Solaris 9 4/03 Operating Environment Might Disable Existing Secure Shell Daemon (sshd) (4626093)

If you upgrade to the Solaris 9 4/03 operating environment on a system that is running a third-party Secure Shell, such as OpenSSH, from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, the Solaris 9 4/03 upgrade software overwrites the contents of /etc/init.d/sshd.

Workaround: Choose one of the following workarounds.

  • If you do not want the Secure Shell protocol server program on your system, do not install the SUNWsshdr and SUNWsshdu packages during the upgrade.

  • If you do not want the Secure Shell protocol server or client programs on your system, do not install the Secure Shell Cluster (SUNWCssh) during the upgrade.

Upgrade Fails if /export Is Near Capacity (4409601)

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


WARNING: Insufficient space for the upgrade.

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

  • Rename the /export directory temporarily, 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 Solstice AdminSuiteTM 2.3 Diskless Client tool, you must perform two steps. 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 4/03 operating environment. For specific instructions, see the System Administration Guide: Basic Administration.

If you attempt to install the Solaris 9 4/03 operating environment over existing diskless clients, the following error message might be displayed:


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.

Installation Bugs That Occur After an Upgrade

SPARC: Removing Patches After Upgrade Might Corrupt WBEM Repository (4820614)

The WBEM Repository CIM database can be corrupted under the following conditions:

  • You apply a revision of patch 112945 for a Solaris 9 Update Release to a system that is running the Solaris 9 operating environment.

  • You then remove the patch that was applied to the system.

If the WBEM Repository is corrupted, the following error message is displayed in the Solaris Management Console Log Viewer:


CIM_ERR_FAILED:
/usr/sadm/lib/wbem/../../../../var/sadm/wbem/logr/
preReg/PATCH113829install/Solaris_Application.mof,18,ERR_SEM,
ERR_EXC_SET_CLASS,CIM_ERR_FAILED:Other Exception:
java.io.StreamCorruptedException: invalid stream header

Workaround: Choose one of the following workarounds.

  • Follow these steps to prevent the WBEM Repository from being corrupted.

    1. Become superuser.

    2. Before you apply the patch, back up the WBEM Repository.


      # cp -r /var/sadm/wbem/logr path/logr

      where path is the path to the backup WBEM Repository.

    3. If the WBEM Repository is corrupted after you back out the patch, stop the WBEM server.


      # /etc/init.d/init.wbem stop

    4. Restore the backup WBEM Repository.


      # cp -rf path/logr /var/sadm/wbem/logr

    5. Restart the WBEM server.


      # /etc/init.d/init.wbem start

  • Follow these steps to create a new WBEM Repository.

    Note –

    This workaround does not restore the WBEM data if the WBEM Repository is corrupted. Any data that was added to the repository during the installation is lost.

    1. Become superuser.

    2. Stop the WBEM server.


      # /etc/init.d/init.wbem stop

    3. Remove the files from the /logr directory.


      # rm /var/sadm/wbem/logr/*

    4. Remove the /notFirstTime directory.


      # rmdir notFirstTime

    5. Start the WBEM server.


      # /etc/init.d/init.wbem start

    6. Manually compile any proprietary Managed Object Format (MOF) files.


      # /usr/sadm/bin/mofcomp MOF-filename

64–Bit Solaris Issues

SPARC: 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 4/03 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 SunTM or UltraSPARC system, the flash PROM update is not needed.

The following table lists the UltraSPARC (Sun4UTM) 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

System Type From uname -i

Minimum Firmware Version From prtconf -V

SUNW,Ultra-1-Engine

3.10.0

SUNW,Ultra-1

3.11.1

SUNW,Ultra-2

3.11.2

SUNW,Ultra-4

3.7.107

SUNW,Ultra-Enterprise

3.2.16

Note –

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

For instructions on how to perform 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 Issue

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 4/03 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 4/03 Documentation CD 1 of 2 is located in the following directory:


sol_9_doc_1of2/README/C/install_C.html

Documentation CD Installation Bugs

Uninstall Mode of Solaris 9 4/03 Documentation CD uninstaller Utility Does Not Work Properly (4675797)

If you run the Solaris 9 4/03 Documentation CD uninstaller in Uninstall All mode, the uninstaller removes only those documentation packages that are installed by default.

Workaround: Run the uninstaller in Uninstall Partial mode. Select the specific packages you want to uninstall.

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

If you use the Solaris 9 4/03 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 4/03 Documentation CD installer program. Use the graphical user interface (GUI) mode to install the Solaris 9 4/03 Documentation CD.

Localization Issue That Occurs During Installation

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 Solaris 9 4/03 operating environment 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.

Localization Bugs That Occur During Installation

Solaris 9 Beta Refresh Chinese CDE Font Packages Do Not Upgrade to Solaris 9 4/03 Operating Environment (4653908)

If you upgrade to the Solaris 9 4/03 operating environment on a system that runs the Solaris 9 Beta Refresh operating environment with Simplified Chinese or Traditional Chinese locale support, the upgrade is not completed successfully. The Simplified Chinese and Traditional Chinese CDE font localization packages (SUNWcdft or SUNWhdft) do not upgrade to the appropriate Solaris 9 4/03 packages. The following error message is displayed.


Removing package SUNWcdft:
/a/var/sadm/pkg/SUNWcdft/install/postremove: 
  /a/usr/dt/config/xfonts/zh_CN.EUC: does not exist
/a/var/sadm/pkg/SUNWcdft/install/postremove: 
  /a/usr/dt/config/xfonts/zh_CN.GBK: does not exist
/a/var/sadm/pkg/SUNWcdft/install/postremove: 
  /a/usr/dt/config/xfonts/zh_CN.UTF-8: does not exist
pkgrm: ERROR: postremove script did not complete successfully

Workaround: Before you upgrade to the Solaris 9 4/03 operating environment, remove the appropriate Solaris 9 Beta Refresh postremove files.


# rm /var/sadm/pkg/SUNWcdft/install/postremove
# rm /var/sadm/pkg/SUNWhdft/install/postremove

Upgrading Systems Running Solaris 8 Operating Environment With Full Thai/Russian/Polish/Catalan Support Leaves Invalid Packages on System (4650059)

An upgrade to the Solaris 9 4/03 operating environment on a system that runs the Solaris 8 operating environment with the Solaris 8 Language Supplement CD installed, results in several invalid packages. Thai, Russian, Polish, and Catalan locale packages remain on the system. These locale packages have an ARCH=sparcall value and are not removed during the upgrade to the Solaris 9 4/03 operating environment.

Workaround: Before you upgrade to the Solaris 9 4/03 operating environment, use the Solaris Product Registry application to remove the Solaris 8 Languages Supplement CD packages.