System Administration

This section describes system administration bugs in this Oracle Solaris 10 OS.

Package Database Contains Path Names That Do Not Exist (7054481)

When you run the pkgchk -n command after an upgrade or after performing a Live Upgrade, you might find that several packages contain path names that do not exist. Because of package history issues, the /var/sadm/install/contents file might not correctly reflect the state of some of the upgraded packages for which the files were removed.

You might see error messages similar to these examples:

 ERROR: /usr/jdk/instances/jdk1.6.0/bin/jhsearch
 pathname does not exist

Workaround: Remove the paths from the contents database.

1. Make sure you are in single-user mode with the root role.

2. Remove the paths for any files in the package that cause errors.

   # removef package path

3. Commit the changes.

   # removef -f package

For example:

# removef SUNWjhdev /usr/jdk/instances/jdk1.6.0/bin/jhsearch
# removef SUNWjhdev /usr/jdk/instances/jdk1.6.0/bin/jhindexer
# removef -f SUNWjhdev

SPARC: 64-bit Version of the libsoftcrypto Library Is Slow (7048794)

The 64-bit version of the libsoftcrypto library runs slowly because it does not use the T4 crypto instructions. As a result, applications that use the 64-bit version of the libsoftcrypto library can encounter performance degradation.

patchrm Command Is Not Supported After Applying Patch 144500/144501 (7033240)

If you install kernel patch 144500 on a SPARC based system or patch 144501 on an x86 based system, the existing ZFS storage pools on the system are upgraded. However, if you use the patchrm command to remove the patch after the root pool is upgraded, the system does not boot because the upgraded pool version does not match the running OS. Therefore, if the root pool is upgraded and the patch is removed, the system does not boot.

If an existing nonroot pool is upgraded and the patch is removed, the SMF local file system service goes into maintenance mode because the local ZFS mounts will fail. Therefore, if a non-root pool is upgraded and the patch is removed, the local ZFS mounts fails.

---

Caution - Do not remove this kernel update (KU) patch with the patchrm command.

---

lucreate Introduces Latency on Slower UFS Systems (7051757)

Performing a live upgrade on a slower UFS system by using the lucreate command takes more time.

The Availability Suite Module sdbc Fails to Load During Boot (6952222)

In this Oracle Solaris 10 release, the sdbc module fails to load during boot and gives the following error message:

[ID 819705 kern.notice]/usr/kernel/drv/sparcv9/sdbc: undefined symbol
WARNING: mod_load: cannot load module 'sdbc'

Workaround: Install patch 123246–07 for SPARC based systems and patch 123247–07 for x86 based systems.

Oracle Solaris 10 9/10 Clock Stops on Oracle VM 2.2 (6952499)

Virtual machines (VMs) that are running Oracle Solaris 10 9/10 guests can be subject to the following problems:

• The time of day clock can stop moving forward.

• Sleep can hang.

• The guest VM can hang entirely.

Workaround: The Oracle Solaris guests must be pinned to physical CPUs. Pin the domain's virtual CPUs to the host's physical CPUs as follows:

# xm vcpu-pin domain vcpu cpus

See the xm(1) man page for more information.

SPARC: FKU 137137-xx Patch Does Not Support Third-Party Volume Manager Software

The FKU 137137-xx patch does not support third-party volume manager software, with some exceptions. This lack of support is due to prepatch, postpatch, and postbackout implementation. If you use unsupported third-party volume manager software, you cannot apply the FKU patch. The following error message is displayed during patch installation:

unsupported root slice type xxxxx

Note that the Fujitsu and Veritas Volume Manager software is supported.

Workaround: None.

Oracle Solaris Is Unable to Handle Mode Switches Between Legacy and AHCI Modes for the SATA Controller (6520224)

On systems that have an AHCI compliant SATA controller, the BIOS setup typically enables the controller to be set in AHCI, legacy, or RAID modes. The Oracle Solaris OS supports AHCI and legacy modes.

The SATA mode setting in BIOS must not be changed after an initial Oracle Solaris installation. The SATA mode setting must also not be changed before or after an Oracle Solaris upgrade. If the SATA mode BIOS setting is modified after the Oracle Solaris 10 OS is installed, the system will reset and fail to boot without indicating what led to the failure.

Workaround: If a boot failure occurs as a result of changing the BIOS setting, revert back to the original setting in order to boot the Oracle Solaris OS.

32-bit: Possible Error With Applications When Obtaining the File System State on Large File Systems (6468905)

When run on large file systems, for example, ZFS, applications using the statvfs(2) or statfs(2) functions to get information about the state of the file system exhibit an error. The following error message is displayed:

Value too large for defined data type

Workaround: Applications should use the statvfs64() function instead.

Using the patchadd Command With the -R Option to Specify an Alternative Root Path From Systems That Are Not Zones Aware Should Be Restricted (6464969)

On systems running an Oracle Solaris OS release that is not zones aware, using the patchadd -R command, or any command that accepts the -R option to specify an alternate root path for a global zone that has non-global zones installed, will not work.

In contrast with the error message that is displayed by using the luupgrade [-t, -T, -p, -P] command, no error message regarding the use of appropriate command-level restrictions is displayed in this case.

There is no indication that the -R option did not work. As a result of the failure of the command, Oracle Solaris 10 packages or patches are not installed on any of the installed non-global zones.

This problem occurs while you are installing and uninstalling packages or patches.

For more information, see the following man pages :

• patchadd(1M)

• patchrm(1M)

• pkgadd(1M)

• pkgrm(1M)

Choose one of the following workarounds.

Workaround 1: Upgrade the OS to at least the Solaris 10 1/06 release.

If you are running the Solaris 10 3/05 release, install the following patches to enable the use of commands that accept the -R option to create an alternate root path:

• SPARC: Patch ID 119254-19

• x86: Patch ID 119255-19

Workaround 2: Restrict the use of the patchadd -R command or any command that accepts the -R option to create an alternate root path.

Instead, boot the alternate root, for example, the Oracle Solaris 10 release, as the active OS. Then install and uninstall the Oracle Solaris 10 packages and patches without using the -R option.

Sun Patch Manager Tool 2.0 Incompatible With Previous Versions of the Tool

A system that runs Sun Patch Manager 2.0 can manage remote systems that run Patch Manager, including Sun Patch Manager 1.0.

However, a system with an earlier version of Patch Manager cannot manage remote systems that run Patch Manager 2.0. Earlier versions include the following:

• Sun Patch Manager Base Software 1.x

• Sun Patch Manager 1.0

Cannot Delete Existing Diskless Clients From the System (6205746)

If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:

Failing with error EXM_BMS.

Workaround: Unshare the /export partition before adding the diskless client.

SPARC: smosservice delete Command Does Not Successfully Remove All Service Directories (6192105)

If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.

Workaround: Follow these steps:

1. Make sure that no clients exist that use the service.

   # unshare /export/exec/Solaris_10_sparc.all
   # rm -rf /export/exec/Solaris_10_sparc.all
   # rm -rf /export/exec/.copyofSolaris_10_sparc.all
   # rm -rf /export/.copyofSolaris_10
   # rm -rf /export/Solaris_10
   # rm -rf /export/share
   # rm -rf /export/root/templates/Solaris_10
   # rm -rf /export/root/clone/Solaris_10
   # rm -rf /tftpboot/inetboot.sun4u.Solaris_10

2. If this file server does not provide functions or resources for any other services, remove the following entry from the /etc/bootparams file.

   fs1-24 boottype=:os

3. Remove the following entry from the /etc/dfs/dfstab file.

   # share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr

4. Modify the /var/sadm/system/admin/services/Solaris_10 file.

   • If the file server is not running the Oracle Solaris 10 OS, delete the file.

   • If the file server is running the Oracle Solaris 10 OS, remove all entries after the first three lines. The deleted lines specify the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.