The WBEM Repository CIM database can be corrupted under the following conditions:
You apply one of the following patches from the Solaris 9 9/02, 12/02, or 4/03 operating environment to a system that is running the Solaris 9 operating environment.
Release |
Patch |
---|---|
Solaris 9 9/02 |
112945-03 |
Solaris 9 12/02 |
112945-05 |
Solaris 9 4/03 |
112945-14 |
You then remove any of the previously identified patches that was applied to the system.
If the WBEM Repository is corrupted, the following error message is displayed in the Solaris Management Console Log Viewer.
CIM_ERR_FAILED: /usr/sadm/lib/wbem/../../../../var/sadm/wbem/logr/ preReg/PATCH113829install/Solaris_Application.mof,18,ERR_SEM, ERR_EXC_SET_CLASS,CIM_ERR_FAILED:Other Exception: java.io.StreamCorruptedException: invalid stream header |
Workaround: Choose one of the following workarounds.
Follow these steps to prevent the WBEM Repository from being corrupted.
Become superuser.
Before you apply the patch, back up the WBEM Repository.
# cp -r /var/sadm/wbem/logr path/logr |
In the previous example, path is the path to the backup WBEM Repository.
If the WBEM Repository is corrupted after you back out the patch, stop the WBEM server.
# /etc/init.d/init.wbem stop |
Restore the backup WBEM Repository.
# cp -rf path/logr /var/sadm/wbem/logr |
Restart the WBEM server.
# /etc/init.d/init.wbem start |
Follow these steps to create a new WBEM Repository.
This workaround does not restore the WBEM data if the WBEM Repository is corrupted. Any data that was added to the repository during the installation is lost.
Become superuser.
Stop the WBEM server.
# /etc/init.d/init.wbem stop |
Remove the files from the /logr directory.
# rm /var/sadm/wbem/logr/* |
Remove the /notFirstTime directory.
# rmdir notFirstTime |
Start the WBEM server.
# /etc/init.d/init.wbem start |
Manually compile any proprietary MOFs.
# /usr/sadm/bin/mofcomp MOF-filename |