test

Sun Patch Manager 2.0 Release Notes for the Solaris 9 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.

Note –

The browser interface that was originally released with the Sun Patch Manager 2.0 product for Solaris 9 systems has been withdrawn.

The Patch Manager product will be replaced by the new Sun Update Manager product.

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.

Remote-mode smpatch add Command Cannot Apply a Patch That Supports More Than One Architecture (5060647)

Description:

Some patches can be applied to systems that have different architectures. For such patches, the architecture designation lists each architecture that the patch supports.

You cannot use the remote-mode smpatch add command to apply this kind of a patch to a system.


$ smpatch add -u root -i 116126-03
Authenticating as user: root
 
Type /? for help, pressing <enter> accepts the default
  denoted by [ ]

Please enter a string value for: password ::
Loading Tool: com.sun.admin.patchmgr.cli.PatchMgrCli
  from mars
Login to mars as user root was successful.
Download of com.sun.admin.patchmgr.cli.PatchMgrCli
  from mars was successful.

Target host architecture is i386. Patch 116126-03 is for
  sparc i386 architecture.

No patches were installed with this command.
Workaround:

Use the local-mode smpatch add command to apply the patch to the system.


# smpatch add -i 116126-03
add patch 116126-03
Patch number 116126-03 has been successfully installed.

Errors Appear During the Patch Manager Postinstallation Reboot (5061986)

Description:

If your system has PatchPro 2.2 installed, the following error messages might appear on the console after you sucessfully install the entire Sun Patch Manager 2.0 product and reboot.

These error messages will only appear once.


Warning at line 5 in file 
/usr/sadm/lib/wbem/../../../../var/sadm/wbem/
  logr/unregDir/pm1cfg/pm1cfg.unreg 
- compilation proceeding ...
Semantic Error:
The following exception was thrown by setInstance: 
CIM_ERR_NOT_FOUND:Element 
"\\root\\system:Solaris_ProviderPath.pathurl=
  \"file:///opt/SUNWsdb/lib/simpledb.jar\"" 
cannot be found.
Adding instance of solaris_providerpath
Warning at line 8 in file 
/usr/sadm/lib/wbem/../../../../var/sadm/wbem/
  logr/unregDir/pm1cfg/pm1cfg.unreg 
- compilation proceeding ...
Semantic Error:
The following exception was thrown by setInstance: 
CIM_ERR_NOT_FOUND:Element 
"\\root\\system:Solaris_ProviderPath.pathurl=
  \"file:///opt/SUNWppro/lib/patchpro.jar\"" 
cannot be found.
Adding instance of solaris_providerpath
Warning at line 11 in file 
/usr/sadm/lib/wbem/../../../../var/sadm/wbem/
  logr/unregDir/pm1cfg/pm1cfg.unreg 
- compilation proceeding ...
Semantic Error:
The following exception was thrown by setInstance: 
CIM_ERR_NOT_FOUND:Element 
"\\root\\system:Solaris_ProviderPath.pathurl=
  \"file:///opt/SUNWapcy/lib/authpcy.jar\"" 
cannot be found.
Compilation succeeded.
Cause:

These errors appear if the PatchPro 2.2 software was installed on your system and you never ran the smpatch command.

In this case, the CIM database has not stored a classpath entry for the unbundled libraries, which causes the CIM_ERR_NOT_FOUND errors.

Later, when Patch Manager is installed, the Patch Manager installation program attempts to remove obsolete classpath entries from CIM.

Workaround:

Ignore these error messages.

Incomplete Definition of Dependency in the Online Glossary of the Browser Interface (5059959)

Description:

The definition of dependency in the online glossary, which you access from the Patch Manager browser interface, is incomplete.

The definition should read as follows:

See patch dependency.

A Local Patch Server Configured on a Solaris 9 System Ignores the Proper Download and Cache Directories (5066628)

Description:

If you are running the local patch server software on a system installed with Solaris 9, the detectors, database, and patches are downloaded to the wrong directories.

The detectors and database are downloaded to /var/sadm/spool/cache instead of /var/sadm/spool/patchsvr/Misc.

Patches are downloaded to /var/sadm/spool instead of /var/sadm/spool/patchsvr/Patches.

Even though the local patch server is using the wrong directories, proper operation is unaffected.

Note that this situation only occurs with systems that run the initial Solaris 9 software. Subsequent Solaris 9 releases are unaffected.