Solaris 9 12/02 Release Notes

System Administration Bugs

IA: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757)

You are booting a Sun LX50 which has a Service partition and the Solaris 9 12/02 (x86 Platform Edition) operating environment is installed. You are given the option of pressing the F4 function key to boot the Service partition. However, pressing F4 causes the screen to go blank and the system fails to boot the Service partition.

Workaround: Do not press the F4 key when the BIOS Bootup Screen is displayed. After a time-out period, the Current Disk Partition Information screen is displayed. Select the number in the Part# column that corresponds to type=DIAGNOSTIC and press the Return key. The system boots the Service partition.

UltraSPARC II CP Event Message in Solaris 9 12/02 Operating Environment Not Always Produced (4732403)

In the Solaris 9 12/02 operating environment, on UltraSPARC II based systems, the CP Event message that accompanies some Uncorrectable Memory Error messages is not always produced. These systems include the Sun Enterprise^TM 10000 and Sun Enterprise 6500/6000/5500/5000/ 4500/4000/3500/3000 systems. The result is that some information needed to identify a failing CPU might not always be present.

Workaround: For the latest information regarding this issue, check the SunSolve Web site at http://sunsolve.sun.com.

Solaris WBEM Services 2.5 Daemon Cannot Locate `com.sun` Application Programming Interface Providers (4619576)

The Solaris WBEM Services 2.5 daemon cannot locate providers that are written to the com.sun.wbem.provider interface or to the com.sun.wbem.provider20 interface. Even if you create a Solaris_ProviderPath instance for a provider that is written to these interfaces, the Solaris WBEM Services 2.5 daemon does not locate the provider.

Workaround: To enable the daemon to locate such a provider, stop and restart the Solaris WBEM Services 2.5 daemon.

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

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

Note -

If you use the javax API to develop your provider, you do not need to stop and restart the Solaris WBEM Services 2.5 daemon. The Solaris WBEM Services 2.5 daemon dynamically recognizes javax providers.

Some `com.sun` Application Programming Interface Method Invocations Fail Under XML/HTTP Transport Protocol (4497393, 4497399, 4497406, 4497411)

If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only CIM remote method invocation (RMI) is fully supported. Other protocols, such as XML/HTTP, are not guaranteed to work completely with the com.sun application programming interface.

The following table lists examples of invocations that execute successfully under RMI but fail under XML/HTTP.

Method Invocation	Error Message
`CIMClient.close()`	`NullPointerException`
`CIMClient.execQuery()`	`CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED`
`CIMClient.getInstance()`	`CIM_ERR_FAILED`
`CIMClient.invokeMethod()`	`XMLERROR: ClassCastException`

Cannot Modify File-System Mount Properties With Solaris Management Console Mounts and Shares Tool (4466829)

The Solaris Management Console Mounts and Shares tool cannot modify mount options on system-critical file systems such as / (root), /usr, and /var.

Workaround: Choose one of the following workarounds.

Use the remount option with the mount command.
# mount -F file-system-type -o remount,additional-mount-options \ device-to-mount mount-point
Note -
Mount property modifications that are made by using the -remount option with the mount command are not persistent. In addition, all mount options that are not specified in the additional-mount-options portion of the previous command inherit the default values that are specified by the system. See the man page mount_ufs(1M) for more information.
Edit the appropriate entry in the /etc/vfstab file to modify the file-system mount properties, then reboot the system.

CIM_ERR_LOW_ON_MEMORY Error Occurs When Trying to Add Data With WBEM (4312409)

The following error message is displayed when memory is low:

CIM_ERR_LOW_ON_MEMORY

You cannot add more entries when the Common Information Model (CIM) Object Manager is low on memory. You must reset the CIM Object Manager Repository.

Workaround: To reset the CIM Object Manager Repository, follow these steps.

Become superuser.
Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop
Remove the JavaSpaces^TM log directory.
# /bin/rm -rf /var/sadm/wbem/log
Restart the CIM Object Manager.
# /etc/init.d/init.wbem start
Note -
When you reset the CIM Object Manager Repository, you lose any proprietary definitions in your data store. You must recompile the MOF files that contain those definitions by using the mofcomp command. See the following example.
# /usr/sadm/bin/mofcomp -u root -p root-password your-mof-file