Installation Bugs That Occur During an Upgrade (Solaris 9 12-03 Release Notes) – Sun Microsystems

Installation Bugs That Occur During an Upgrade

Upgrade Fails to Install SUNWceudt Package (4826785)

If you are upgrading to the Solaris 9 12/03 OS from a previous Solaris 9 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 12/03 DVD or the Solaris 9 12/03 Software 1 of 2 CD to add back the SUNWceudt package. Follow these steps:

Become superuser.

Remove the SUNWceudt package.

# pkgrm SUNWceudt

 

Change directories to the product directory.

# cd path-to-Solaris-9/Product

Add the SUNWceudt package.

# pkgadd -d `pwd` SUNWceudt

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 installation.

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:

Set the C locale.

# LANG=C; export LANG

Begin the installation.

If you are using the C shell, follow these steps:

Type the following:

# csh

 

Set the C locale.

# setenv LANG C

 

Begin the installation.

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

When you upgrade from the Solaris 8 software to the Solaris 9 or the Solaris 9 12/03 release, 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 to Solaris 9 12/03 Release Might Disable Existing Secure Shell Daemon (sshd) (4626093)

If you upgrade to the Solaris 9 12/03 release 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 12/03 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 Directory Is Near Capacity (4409601)

If the /export directory is near capacity when you upgrade to the Solaris 9 12/03 release, space requirements for /export are miscalculated. The upgrade then fails. This problem commonly occurs if a diskless client is installed. Another instance of when the problem occurs is when 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 the following two steps:

Delete all existing diskless clients that are the same Solaris version and architecture as the server.

Install or upgrade to the Solaris 9 12/03 release.

For specific instructions, see the System Administration Guide: Basic Administration.

If you attempt to install the Solaris 9 12/03 software 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 software.