test

Sun Patch Manager 2.0 Release Notes for the Solaris 8 Operating System

Chapter 1 Sun Patch Manager 2.0 Runtime Issues and Bugs

This chapter describes runtime issues and bugs that are known to be problems in the SunTM Patch Manager 2.0 product (Patch Manager). Issues include information that you need to know about, including prerequisites, tips, troubleshooting hints, and bugs. Bugs are a subset of issues and include tracking numbers in parentheses.

Sun Patch Manager 2.0 Interoperability

A system that runs Sun Patch Manager 2.0 can manage remote systems that run Patch Manager, including SolarisTM Patch Manager 1.0.

However, a system that runs an earlier version of Patch Manager, such as Solaris Patch Manager Base 1.x or Solaris Patch Manager 1.0, cannot manage a system that runs Sun Patch Manager 2.0.

Note that a Solaris 8 system cannot manage other systems or be managed by other systems, as there is no Solaris 8 CIM/WBEM support for Patch Manager.

No Reboot Prompt Appears When Using the Browser Interface to Remove Kernel Patches (4960505)

Description:

When you use the Sun Patch Manager 2.0 browser interface to apply a kernel patch, you are prompted to reboot the system to make the patch take affect.

However, when you use the browser interface to remove a kernel patch, you are not prompted to reboot the system.

Workaround:

After removing a kernel patch, manually reboot the system to bring the system to a stable state.

Analysis Recommends a Patch That Cannot Be Applied Due to Patch Dependencies and the Policy for Applying Patches (5009098)

Description:

Sometimes a patch analysis recommends a patch that cannot be applied.

This situation occurs when the following are true:

  • The patch depends on a prerequisite patch that has been obsoleted by another patch.

  • The replacement prerequisite patch is not permitted to be applied because it is prohibited by the policy for applying patches.

Workaround:

Do the following:

  1. Manually apply the replacement prerequisite patch that is prohibited by the policy for applying patches while the system is in single-user mode.

  2. Reboot the system.

  3. Use smpatch or the browser interface to apply the patch that was recommended by the analysis.