JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Basic Administration     Oracle Solaris 10 8/11 Information Library
search filter icon
search icon

Document Information

About This Book

1.  Oracle Solaris Management Tools (Road Map)

2.  Working With the Solaris Management Console (Tasks)

3.  Working With the Oracle Java Web Console (Tasks)

4.  Managing User Accounts and Groups (Overview)

5.  Managing User Accounts and Groups (Tasks)

6.  Managing Client-Server Support (Overview)

7.  Managing Diskless Clients (Tasks)

8.  Introduction to Shutting Down and Booting a System

9.  Shutting Down and Booting a System (Overview)

10.  Shutting Down a System (Tasks)

11.  Modifying Oracle Solaris Boot Behavior (Tasks)

12.  Booting an Oracle Solaris System (Tasks)

13.  Managing the Oracle Solaris Boot Archives (Tasks)

14.  Troubleshooting Booting an Oracle Solaris System (Tasks)

15.  x86: GRUB Based Booting (Reference)

16.  x86: Booting a System That Does Not Implement GRUB (Tasks)

17.  Working With the Oracle Solaris Auto Registration regadm Command (Tasks)

18.  Managing Services (Overview)

19.  Managing Services (Tasks)

20.  Managing Software (Overview)

21.  Managing Software With Oracle Solaris System Administration Tools (Tasks)

22.  Managing Software by Using Oracle Solaris Package Commands (Tasks)

23.  Managing Patches

About Patches

Patching Strategy

Live Upgrade

Applying an Oracle Solaris Update or an Oracle Solaris Update Patch Bundle

Applying a Recommended Patch Cluster

Applying a Critical Patch Update

Applying an Enterprise Installation Standards Patch Baseline

Downloading a Patch

How to Search for a Patch

Displaying Information About Patches

Applying a Patch

How to Apply a Patch Using the patchadd Command

Removing a Patch

Patch Management Terms and Definitions

A.  SMF Services


Patch Management Terms and Definitions

The following terms are used throughout the patch management chapters.


To install a patch on a system.

back out

To remove a patch from a system.

backout data

Data that is created when a patch is applied to enable the system to return to its previous state if the patch is removed (backed out).

backout directory

Directory in which backout data is stored. By default, this is the save directory of each package that was installed by the patch.


See patch dependency.

digital signature

An electronic signature that can be used to ensure that a document has not been modified since the signature was applied.


To copy one or more patches from a source of patches to the system where the patches are to be applied.

download directory

Directory in which patches are stored when they are downloaded from the patch source. This is also the directory from which patches are applied. The default location is /var/sadm/spool.


A repository of certificates and keys that is queried when you attempt to apply a signed patch.

nonstandard patch

A patch that cannot be installed by using the patchadd command. A nonstandard patch is not delivered in package format. This patch must be installed according to the instructions specified in the README file of the patch. A nonstandard patch typically delivers firmware or application software fixes.


To sort a set of patches in an order suitable for applying patches.


The form in which software products are delivered for installation on a system. The package contains a collection of files and directories in a defined format.


An update to software that corrects an existing problem or that introduces a feature.

patch analysis

A method of checking a system to determine which patches are appropriate for the system.

patch dependency

An instance where a patch depends on the existence of another patch on a system. A patch that depends on one or more patches can only be applied to a system when those other patches have already been applied.

patch ID

A unique alphanumeric string, with the patch base code first, a hyphen, and a number that represents the patch revision number.

patch incompatibility

A rare situation where two patches cannot be on the same system. Each patch in the relationship is incompatible with the other. If you want to apply a patch that is incompatible with a patch already on the system, you must first remove the patch that is already on the system. Then, you can apply the new patch.

patch list

A file that contains a list of patches, one patch ID per line. Such a list can be used to perform patch operations. The list can be generated based on the analysis of a system or on user input.

Each line in a patch list has two columns. The first column is the patch ID, and the second column is a synopsis of that patch.

patch server

A source of patches that can be used by your systems to perform patch analyses and from which they obtain the appropriate patches.

software update

A change to software that you apply that corrects an existing problem or that introduces a feature.

special handling

Patches with properties that indicate they must be installed in single-user mode. Also, patches that require you to restart the system after the patch has been applied are referred to as having special handling requirements.

standard patch

Standard patches are those that adhere to the Oracle Solaris patch specification and are installable by using the patchadd command. Note that nonstandard patches cannot be installed by using the patchadd command

superseded patch

An instance where a patch replaces another patch even if it has not already been applied to a system. For example, if a patch X is marked as superseded, then there exists a patch Y that contains the fixes of patch X. In this example, patch Y replaces the superseded patch X completely. You do not need to apply patch X unless patch X is required for a specific purpose.