Solaris 9 9/05 Release Notes

Installation Bugs That Occur After an Upgrade

The following installation bugs occur after you upgrade to the Solaris 9 9/05 release.

Obsolete Uninstallers Not Removed When You Use Solaris Live Upgrade to Upgrade From Previous Solaris Releases (6198380)

Obsolete uninstaller programs are not removed if you use Solaris Live Upgrade to upgrade to Solaris 9 9/05 OS from the following releases:

Solaris 8 OS
Solaris 9 releases previous to Solaris 9 9/05 OS

These uninstaller programs from the previous OS remain in the system's /var/sadm/prod directory.

The following obsolete uninstallers are not removed.

uninstall_Alternate_Pathing_2_3_1.class
uninstall_CDRW_1_1.class
uninstall_CDRW_1_0.class
uninstall_Java3D_1_3.class
uninstall_Java3D_1_2_1_04.class
uninstall_Java3D_1_2_1_03.class
uninstall_Man_Page_Supplement.class
uninstall_OpenGL_1_2_3.class
uninstall_Netscape_6_2_3.class
uninstall_Netscape_6_2_1_Beta.class
uninstall_PC_launcher_1_0_2.class
uninstall_PC_launcher_1_0_1_PCfileviewer_1_0_1.class
uninstall_RSC_2_2_2.class
uninstall_RSC_2_2_1.class
uninstall_RSC_2_2.class
uninstall_ShowMeTV_1_3.class
uninstall_Sun_Hardware_AnswerBook.class
uninstall_SunATM_5_0.class
uninstall_SunFDDI_PCI_3_0.class
uninstall_SunFDDI_SBus_7_0.class
uninstall_Sun_Fire_880_FC-AL_Backplane_Firmware_1_0.class
uninstall_SunForum_3_1.class
uninstall_SunVTS_5_1_PS6.class
uninstall_SunVTS_5_1_PS5.class
uninstall_SunVTS_5_1_PS4.class
uninstall_SunVTS_5_1_PS3.class
uninstall_SunVTS_5_1_PS2.class
uninstall_SunVTS_5_1_PS1.class
uninstall_SunVTS_5_0.class
uninstall_System_Management_Services_1_4.class
uninstall_System_Management_Services_1_3.class
uninstall_System_Management_Services_1_2.class
uninstall_WBEM_DR_1_0.class
uninstall_Web_Start_Wizards_SDK_3_0_1.class
uninstall_Web_Start_Wizards_SDK.class

Workaround: After you upgrade the system, manually remove the obsolete uninstallers in the /var/sadm/prod directory.

SPARC: After Upgrading or Applying Recommended Patches, Problems With SAM-FS/QFS Occur (5003346)

The SAM-FS/QFS daemons do not start and the file systems are unmountable if you performed either of the following operations:

You upgraded to Solaris 9 4/04 Release.
You applied the Solaris 9 Recommended Patch Cluster (Solaris 9 patch ID 112233-11).

The error occurs because system call 181 that the daemons normally use is being used by a different module. The module was introduced by the patch that you had just applied. The following error messages are recorded in /var/adm/messages :

/var/adm/messages
 Jan  5 13:28:46 host genunix: [ID 147998 kern.warning] WARNING: system 
 call entry 181 is already in use
 Jan  5 13:28:46 host samfs: [ID 798779 kern.warning] WARNING: SAM-FS: 
 modload(samsys) failed.

In addition, the following error messages are also recorded in /var/adm/sam-log :

/var/adm/sam-log
 Jan  5 13:30:08 host sam-fsd[355]: [ID 617651 local4.alert] Fatal error -
 samsys module not loaded
 Jan  5 13:30:08 host sam-fsd[355]: [ID 765074 local4.alert]   Correct 
 problem and 'kill -HUP 355'

Perform the following steps:

Become superuser.

Issue a grep of 181 from the modinfo output to determine if 181 is in use by another module:

# modinfo | grep 181
     8  1181aa0   38c4   1   1  TS (time sharing sched class)
    15  11b1092   181a  12   1  sad (STREAMS Administrative Driver ')
    43  1295cd8    ce9 181   1  ssc050 (SSC050 i2c device driver: v1.4)
   158 7813a87f   181c  95   1  cpc (cpc sampling driver v1.10)
   158 7813a87f   181c 179   1  cpc (cpc sampling system call)
   158 7813a87f   181c 179   1  cpc (32-bit cpc sampling system call)

Because system call 181 is used by another module, configure samsys to use another unused system call value.

Edit /etc/name_to_sysnum by changing samsys to use 182 or some other unused value from 0-255.
samsys 182
Boot the system to reconfigure samsys.

# shutdown -y -g0 -i0

OK> boot -r
Verify that the error messages no longer appear in /var/adm/messages and that all SAM-FS file systems can mount.

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
  # 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