This section describes system administration bugs in the Oracle Solaris 10 OS.
In this 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 systems and patch 123247–07 for x86 systems.
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 workaround is to require Oracle Solaris guests to 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.
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
However, the Fujitsu and Veritas Volume Manager software is supported.
Note - This bug is applicable if you are mounting the Solaris 10 10/09 or a later release DVD media on systems running on earlier Oracle Solaris releases. Use the following vold patches to mount the DVD media on systems running on older Oracle Solaris releases:
138130–01 for Oracle Solaris 10 (SPARC systems)
138131–01 for Oracle Solaris 10 (x86 systems)
112966–07 for Solaris 9 (SPARC systems)
115021–05 for Solaris 9 (x86 systems)
108968–12 for Solaris 8 (SPARC systems)
108969–12 for Solaris 8 (x86 systems)
The Solaris 10 10/09 DVD does not mount by default during runtime. No error message is displayed.
Workaround: Perform the following steps:
On Oracle Solaris 10 Systems:
# svcadm disable -t volfs
On Solaris 8 and Solaris 9 systems:
Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
# mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt
In systems which have an AHCI compliant SATA controller, the BIOS setup typically enables the controller to be set in either AHCI, legacy, or RAID modes. 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 installing Oracle Solaris 10, the system will reset and fail to boot without indicating what led to the failure.
Workaround: If boot failure is encountered as a result of changing the BIOS setting, revert back to the original setting in order to boot the Oracle Solaris OS.
When run on large file systems, for example ZFS, applications using statvfs(2) or statfs(2) 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 statvfs64() instead.
On systems running an Oracle Solaris release that is not zones aware, using patchadd -R, 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 instance.
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 installing and uninstalling packages or patches.
Note - The -R option works if the alternate boot environment has configured non-global zones, but no installed non-global zones. However, to avoid a potential problem, or if you are not sure whether there are any installed non-global zones used as the alternate root path, restrict the use of the -R option in all instances.
For more information, see the following man pages :
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:
Patch ID 119254-19 for SPARC based systems
Patch ID 119255-19 for x86 based systems
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.
A system that runs the Sun Patch Manager Tool 2.0 can manage remote systems that run Patch Manager Tool, including Sun Patch Manager Tool 1.0.
However, a system with an earlier version of Patch Manager Tool cannot manage remote systems that run Patch Manager Tool 2.0. Earlier versions include the following:
Sun Patch Manager Base Software 1.x
Sun Patch Manager Tool 1.0
Note - Common Information Model/Web Based Enterprise Management (CIM/WBEM) support for Patch Manager Tool does not exist in the Solaris 8 OS. Consequently, remote management with Patch Manager does not apply to Solaris 8 systems.
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 client.
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.
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
Remove the following entry from the /etc/bootparams file.
Note - Remove this entry only if this file server does not provide functions or resources for any other services.
Remove the following entry from the /etc/dfs/dfstab file.
share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr
Modify the /var/sadm/system/admin/services/Solaris_10 file.
If the file server is not Oracle Solaris 10, delete the file.
If the file server is Oracle Solaris 10, remove all entries after the first three lines. The deleted lines indicate the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.