Installation Bug That Occurs After an Upgrade

SPARC: Removing Patches After Upgrade Might Corrupt WBEM Repository (4820614)

The WBEM Repository Common Information Model (CIM) database can be corrupted under the following conditions:

• You apply a revision of patch 112945 for a Solaris 9 release to a system that is running the Solaris 9 software.

• You then remove the patch 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:

  1. Become superuser.

  2. Before you apply the patch, back up the WBEM Repository.

     # cp -r /var/sadm/wbem/logr path/logr

     where path is the path to the backup WBEM Repository.

  3. If the WBEM Repository is corrupted after you back out the patch, stop the WBEM server.

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

  4. Restore the backup WBEM Repository.

     # cp -rf path/logr /var/sadm/wbem/logr

  5. Restart the WBEM server.

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

• Follow these steps to create a new WBEM Repository:

  ---

  Note –

  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.

  ---

  1. Become superuser.

  2. Stop the WBEM server.

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

  3. Remove the files from the /logr directory.

     # rm /var/sadm/wbem/logr/*

  4. Remove the /notFirstTime directory.

     # rmdir notFirstTime

  5. Start the WBEM server.

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

  6. Compile any proprietary Managed Object Format (MOF) files manually.

     # /usr/sadm/bin/mofcomp MOF-filename