Solaris patches installation

The backout script displays a message similar to the patchadd command, except on a system that has only the Access Manager SDK component installed. Then, run the following command, which is shown with Access Manager installed in the default directory on Solaris systems:. For additional information and examples about the patchadd and patchrm commands, see the appropriate Solaris man pages. If Access Manager is installed in a local zone, the patchadd -G option has no effect.

If you are installing Access Manager 7. Similarly, if Access Manager is installed in the global zone, the -G option is required to run the patchrm command. For example: patchrm The backout script displays a message similar to the patchadd command, except on a system that has only the Access Manager SDK component installed.

When you add a patch, the patchadd command calls the pkgadd command to install the patch packages from the patch directory to a local system's disk. More specifically, the patchadd command:.

Updates the patch package's pkginfo file with information about patches obsoleted by the patch being installed, other patches required by this patch, and patches incompatible with this patch. The patch is incompatible with another, already installed patch. Each installed patch keeps this information in its pkginfo file. This procedure assumes that you have already pulled the patch from one of the sites listed in Accessing Solaris Patches.

Or, you can download the patch and use the ftp command to copy the patch to the target system. Determine if you are going to download a recommended a specific patch or patch cluster. For example, if you did not add SRU 28 repository content to your local repository, but you did add SRU 29 repository content, you would have all fixes that were initially delivered in any SRU for this release through SRU 29, but you would not be able to update systems to the SRU 28 level.

A query would show that your local repository does not contain [email protected] , even though it does contain [email protected]. See Check Available Versions. The following critical patch update package is available with each monthly SRU. The solariscpu package is not installed by default. If you want this package, you must explicitly install it.

This package is not required in order to update to a newer SRU. Advantages to installing this package include:. Easily upgrade to a specific SRU by updating this package to that specific version.

All components are moved to the specified SRU level, including any components that are unlocked from their constraint packages. The following command lists all CVE fixes that are installed on this system if this system has the solariscpu package installed:. If this system does not have the solariscpu package installed, identify the solariscpu package for the SRU that is installed, and query that package remotely.

For example, if this system is running Oracle Solaris To check whether additional fixes are available, use the following command to show whether a version of the solariscpu package is available that is newer than the version you have installed:.