Patching endpoints on Solaris 10 and earlier

When deploying patches, the required packages are downloaded from the Oracle repository by using the download plug-in. For Critical Patch Update (CPU) and the Recommended Patch Cluster, you can use a local repository to host the packages and share them across your network using Network File System (NFS).

Before you begin

  • BigFix Patch for Solaris uses Bourne shell scripts to install packages on the endpoints. Ensure that an sh-compatible shell is installed on the endpoints to successfully patch using Fixlets.
  • If you want to deploy patches by using the internet download method by using the download plug-in, complete the following steps:
    • Register the Solaris Download plug-in. For more information about download plug-ins, see Download Plug-ins.
    • For Recommended Patch Clusters and Critical Patch Updates, use the Solaris 10: Insufficient Disk Space - /var task (ID #3) to check whether the file system that contains /var has sufficient space to extract and install the patches.
  • If you want to deploy patches through an NFS share, complete the following steps:
    1. Run the Enable NFS Support - Solaris 10 task to enable the NFS protocol.
    2. Run the Add NFS Share - Solaris 10 task to add the path to the NFS share. You can add a persistent or non-persistent share with different access levels.
    Both these tasks are available on the Patching Support site.


  1. In the All Patch Management Content node of the navigation tree, click Fixlets and Tasks > By Site.
  2. Depending on what you want to patch, select the appropriate site.
    • Patches for Solaris site
    • Patches for Solaris Live Upgrade site
    Tip: It is suggested that you deploy the latest Critical Patch Updates (CPU) Fixlets before you deploy the Fixlets for the Patch Clusters.
    Note: The Oracle Recommended Patch Clusters are updated frequently. The patch vendor updates cause the sha1 value and the size of the patch bundle to change. The frequent patch updates might cause the Fixlets for the Patch Clusters to fail. Updated Fixlets are provided based on the service-level agreement with the patch vendor.
  3. View the available content in the list panel and double-click the Fixlet that you want to deploy.
  4. Review the text in the Description tab.
  5. Click the appropriate link in the Actions box to start the deployment.
    Note: If you decide to deploy the patches for Critical Patch Update (CPU) and Recommended Patch Cluster from an accessible NFS share, enter the full path to the NFS repository. For example, "myServer:/Solaris/fileset repo" myServer:/Local/Repo.
  6. Click OK.