After upgrading a server with diskless clients of more than one SPARC kernel architecture, such as a sun4u server with diskless sun4c, sun4d, and sun4m clients, the SUNWkvm packages for clients whose kernel architectures differ from that of the server cannot be patched.
Workaround: Add all of the SUNWkvm packages before applying any patches that affect them:
# pkgadd -d SUNWkvm.*
The upgrade program can exaggerate by as much as 30 percent the amount of space required for upgrades to systems with the Solaris software. Therefore, it prevents many systems from being upgraded without deselecting packages or finding more space.
Workaround: You can manually reallocate disk space among file systems or use the Software Customization menu to remove software packages that are not needed.
Patches located in the Patches directory on the Solaris 7 8/99 CD are not automatically applied to clients whenever a server is upgraded.
Workaround: Apply the patches located in the Patches directory to clients after the upgrade has been completed.
After upgrading from the Solaris 7 3/99 or 5/99 operating environments to the Solaris 7 8/99 operating environment, the following errors may appear in the upgrade logs:
Doing pkgadd of SUNWplow to /. pkgadd: ERROR: unable to create package object </a/usr/openwin/share/locale/de.ISO8859-15>. file type <s> expected <d> actual unable to remove existing directory at </a/usr/openwin/share/locale/de.ISO8859-15> .... Installation of <SUNWplow> partially failed. pkgadd return code = 2 Doing pkgadd of SUNWpldte to /. WARNING: /a/usr/dt/appconfig/types/de.ISO8859-15 may not overwrite a populated directory. ...... pkgadd: ERROR: /a/usr/dt/appconfig/types/de.ISO8859-15 could not be installed. ....... Installation of <SUNWpldte> partially failed. pkgadd return code = 2
This warning occurs because the patch switches the affected directories listed in the upgrade logs from symbolic links to directories. The upgrade process then attempts to install an updated version of the package that does not include the change. These errors do not affect the operating environment on your system.
Workaround: Ignore these error messages.
An upgrade using disk space reallocation in which the /usr partition is resized or moved causes some language packages to be removed from the system. The packages appear in the package database as installed, but the language files are not installed on the file system.
This does not occur on systems installed with only the English language.
Workaround: You may choose one of the following workarounds:
To manually adjust file system sizes before upgrading:
Back up the system.
Using the format command, adjust the file system sizes according to the requirements described in the install program.
Restore the system on to the new file systems.
Start the upgrade. The upgrade will proceed without disk space reallocation as you have adjusted the file systems so that there is enough space to complete the upgrade.
To install the missing packages after the upgrade is complete:
Determine which packages are missing. The missing packages are those that do not appear in the do_pkgadd lines in the /var/sadm/system/admin/upgrade_script and who have non-empty lines in SUNW_LOC in their pkginfo files in the /var/sadm/pkg directory.
Create an admin file as /tmp/admin with the following lines:
For detailed instructions about creating an admin file, refer to admin(4).
Install the missing packages by typing the following command for each package to install:
# pkgadd -a /tmp/admin -d /cdrom/cdrom0/Solaris_2.7/Product package_name
where package_name is the name of the package to install.
If your Solaris 7 8/99 software is mounted somewhere other than the CD-ROM drive, change the argument to the -d option to be the absolute path to the Solaris_2.7/Product directory.
After upgrading from the Solaris 7 operating environment using disk space reallocation, the java commands may not be found due to missing symbolic links.
Workaround: To restore the symbolic links, complete these steps: