Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
 Contact HP
HP.com home
HP Tru64 UNIX Version 5.1B-2 and Higher: Patch Kit Installation Instructions > Chapter 3 Patch Installation and Removal Instructions

Removing Patches


Table of Contents
Content starts here

To remove patches from your system, use the Patch Deletion option of the dupatch Main Menu. The following sections describe actions describe the patch removal process.


Beginning with the version of dupatch delivered in the Version 5.1B-3 kit, the patch removal process depends upon whether you installed the new form of patch kits, called Inclusive Patch Kits. These kits began shipping with Version 5.1B-2.

With Inclusive Patch Kits you must remove the entire kit rather than individual patches. However, once you have removed any Inclusive Patch Kits installed on your system, you can then remove individual patches from earlier kits.

To do this, dupatch recognizes the type of kit you have installed. When you select the patch deletion menu, dupatch lists the most current Inclusive Patch Kit installed on your system as well as any customer-specific patches (CSPs) that depend upon that kit.

After you remove that kit and reboot your system, you can rerun dupatch to remove the next most current Inclusive Patch Kit and the CSPs that depend on it.

Once all inclusive patch kits have been removed, the next time you run the patch deletion program, dupatch will list all of the patches on your system and you can selectively remove any of those patches.


With the old-style patch kits, the Patch Deletion menu lists every setld-based patch on your system, regardless of which patch kit installed them. If you select the ALL of the above menu item, it will remove all setld-based patches from your system. Therefore, you want to remove all of the patches from a patch kit, but do not want to delete setld-based patches, you will have to specify the patch ID of all of that kit's patches.

The latest version of dupatch also gives you the option to delete patches in single-user mode or in multi-user mode. As with the installation process, using single-user mode is safer and is the recommended procedure. See “When Single-User Mode Is Recommended” for more information.

The dupatch utility issues the following warning when you are deleting patches in multi-user mode.

*** Multi-User Deletion Warning ***

You have chosen to delete patches from this system while it is running in
Multi-User mode. Some patches may directly affect core operating system
operations. To ensure the proper operation of all applications, it is
strongly suggested that you delete these patches while the system is in
Single-User mode. If this cannot be done, delete these patches when the
system is as lightly loaded as possible (i.e. not running production
environments, no users logged on, etc.).

Do you want to continue? (y/n):

If you want to continue, answer yes. If you do not want to delete the patch kit in multi-user mode, answer no and bring your system down to single-user mode as described in “Installing Patches from Single-User Mode”.

Important Tasks Required Before Removing Patches and Rebooting System

Before running the patch deletion process you may have to perform the tasks described in the following sections.

Run Mandatory Script Before Removing New Style Patch Kits

If you enabled version switches as described in “Enabling the Version Switch After Installing a New Style Patch Kit” for an Inclusive Patch Kit, you must run the /usr/sbin/versw_enable_delete script before attempting to remove the patch kit. The steps for running this script require a complete cluster or single system shutdown, so choose a time when a shutdown will have the least impact on your operations. The following steps describe the procedure:

  1. Make sure that all phases of the patch kit installation process have been completed.

  2. Run /usr/sbin/versw_enable_delete:

    # /usr/sbin/versw_enable_delete
  3. Shut down the entire cluster or the single system.

  4. Reboot the entire cluster or the single system.

  5. Run dupatch on your single system or on a cluster using the rolling upgrade procedure to delete the patch kit.


    The next step requires that you reboot each cluster member to remove the patch kit. Because the no-roll procedure automatically reboots the system after deleting the patches, you would not be able to perform the next steps as required. Therefore, you cannot use the no-roll procedure to remove this patch kit.

  6. Reboot the single system or each member of the cluster.

Changes to System May Need to Be Reversed

If you made the following changes to your system after installing the patch kit, you will have to undo those changes before you can uninstall the patch kit:

  • If you changed your hardware configuration (for example, by adding a new disk), the system configuration that existed prior to installing the patch kit might not recognize the new devices or may not provide the necessary support for them.

  • If you added new cluster members, the new members will not have an older state to revert to if you attempt to uninstall the patch kit.

To uninstall the patch kit, do the following:

  1. Remove all new hardware and new cluster members that you added after installing the patch kit.

  2. Run dupatch to uninstall the patch kit.

  3. Verify that the patch kit was successfully uninstalled.

You can now add the cluster members you removed and reinstall the hardware you removed, as long as the support for it existed in the pre-patched system. You can also reinstall the patch kit.

Script Must Be Run Prior to Reboot on Certain Version 5.1B Systems

If removing a PK4 or higher patch kit restores your Version 5.1B system to a pre-patched state, you must run the script /etc/dn_fix_dat.sh before rebooting your system during the patch deletion process. This would occur if the inclusive patch kit you are uninstalling is the only patch kit installed on your Version 5.1B system

You must also run this script if you are removing a specific patch from previous Version 5.1B patch kits if those kits are the only patch kit on your system. The affected patch in those kits will be noted in a Special Instruction that is displayed when you run the dupatch installation and deletion processes.

Failing to run this script will result in your system being unable to boot normally. If this occurs, do the following:

  1. Boot your system in single-user mode:

     >>> boot -fl s 
  2. Run the script:

    # /etc/dn_fix_dat.sh
  3. Reboot normally.

If you also need to reverse the version switch as described in “Run Mandatory Script Before Removing New Style Patch Kits”, run the /etc/dn_fix_dat.sh script after step 5 in that process.

Running dupatch to Remove Patches

The process for removing patches is similar to the one for installing them.

The following steps describe the patch removal process for an Inclusive Patch Kit with the system running in single-user mode. In mutiuser mode the steps would be the same except you would see the multi-user deletion warning described in “Overview”.

See “Installing Patches from Single-User Mode” for the steps on bringing down your system to single-user mode.

  1. Run dupatch and select 2 for patch removal:

    # /patch/pk4/patch_kit/dupatch
    Tru64 UNIX Patch Utility (Rev. 48-00)
            - This dupatch session is logged in /var/adm/patch/log/session.log
        Main Menu:
        1)  Patch Kit Installation
        2)  Patch Kit Deletion
        3)  Patch Kit Documentation
        4)  Patch Tracking
        5)  Patch Baseline Analysis/Adjustment
        h)  Help on Command Line Interface
        q)  Quit
    Enter your choice: 2
  2. Select the current patch kit. This menu will change if no Inclusive patch kits are installed.

    There may be more patches than can be presented on a single
         screen. If this is the case, you can choose patches screen by screen
         or all at once on the last screen. All of the choices you make will
         be collected for your confirmation before any patches are deleted.
         1) CSP C688.00  drag-and-drop or cut-and-paste may fail
         2) CSP C718.00  Debug version of ping 
         3) CSP C752.00  page on o/h list panic 
         4) CSP C882.00  Fix for memory leak and slowdown in rpc.lockd
         5) T64V51BB26AS0005-20050215 and all CSP's dependent upon it 
    Or you may choose one of the following options:
         2) ALL of the above 
         3) CANCEL selections and redisplay menus
         4) EXIT without deleting any patches 
    Enter your choices or press RETURN to redisplay menus.
    Choices (for example, 1 2 4-6): 7
    You are deleting the following patches:
            T64V51BB26AS0005-20050215 and all CSP's dependent upon it               
    Is this correct? (y/n):y
                    ***  Start of Special Instructions  ***
    If you delete this patch kit, you MUST run the following script prior to 
    rebooting your system:  /etc/dn_fix_dat.sh
  3. You are asked to record your name as the person removing the patches and to add any comments you would like stored for future reference in the log file. For example:

    Your name: Betty

    Enter any notes about this operation that you would like stored for future reference. To end your input, enter a period (.) and press Return.

    : Uninstalling V5.1B-3
    : . Return
    Checking patch dependency...
      (depending upon the number of patches you select, this may take awhile)
       *** The Patch Kit will delete 67 patches ***
    ************************** CAUTION ************************************ 
    	Interruption of this phase of the operation will corrupt your 
    	operating system software and compromise the patch database 
    	DO NOT Ctrl/C, power off your system, or in any other way 
    	interrupt the patch operation. The patch operation is complete 
    	when you are returned to the Patch Utility menus.
    Deleting "Patch: SP05 OSFEXER540" (OSFPAT02603100540).
    Deleting "Patch: SP05 OSFEXAMPLES540" (OSFPAT02603000540).
    Deleting "Patch: SP05 OSFENVMON540" (OSFPAT02602800540).
  4. Rebuild the kernel. This step is the same as for the installation process. See “Rebuilding the Kernel” for details.

  5. Review the session log to ensure the removal was successful. Note any special patch instructions, informational messages, and error messages. This is especially important to identify any actions that you may have to take (such as running a script) before rebooting your system.

  6. Run the script described in “Script Must Be Run Prior to Reboot on Certain Version 5.1B Systems”.

  7. Reboot the system. See “Rebooting the System” for details.

Printable version
Privacy statement Using this site means you accept its terms
2006 Hewlett-Packard Development Company, L.P.