12.7 The Patch shar File

     

12.7 The Patch shar File

Whichever method is used to obtain a patch, a single patch will arrive in what is known as a shell archive or shar file. The UNIX command shar is used to bundle the named files into a single distribution package. The package contains two files:

  1. The patch text README file

  2. The patch software itself, in the form of an SD-UX depot

To unpack the package, use the sh command with the package name as an argument as follows :

 

 root@hpeos004[tmp]  ll PHCO_1000  -rw-r-----   1 root       sys          33624 Sep 25 14:47 PHCO_1000 root@hpeos004[tmp]  file PHCO_1000  PHCO_1000:      shar file root@hpeos004[tmp]  sh PHCO_1000  x - PHCO_1000.depot [non-ascii] x - PHCO_1000.text root@hpeos004[tmp] 

This will unpack the files into the current directory. To this end, it may be appropriate to first put the package into an appropriate directory.

Once unpacked, the patch text file should be analyzed closely. This text file not only contains information relating the symptoms of the defects fixed, but also dependency information. An important section to analyze closely is the installation instructions. Here, you may also find Special Installation Instructions that must be followed.

Should you choose to not follow the instructions ”with particular regard for the Special Installation Instructions ”you may render your systems unusable, difficult to support, or even unbootable. The Special Installation Instructions are there for your benefit and should be followed closely. To illustrate the point, let's look at a particular example.

Below are the Special Installation Instructions for patch PHSS_28849 : MC/ServiceGuard and SG-OPS Edition A.11.13:

 root@hpeos004[tmp]  more PHSS_28849.text  Special Installation Instructions: For ServiceGuard OPS Edition Clusters using OPS 8.0.6, do the following: Halt the cluster. Install this patch on all nodes. Relink Oracle applications on all nodes. On all nodes, add this new line to the Oracle initialization file (usually named init.ora) as follows: ogms_home=/var/opt/ogms Start the cluster and OPS. For ServiceGuard OPS Edition Clusters using OPS 8.1.6 or higher do the following: Halt OPS and ServiceGuard on the node the patch is to be installed on. Install this patch on that node. Restart ServiceGuard and OPS on that node. Patch needs to be installed on all nodes in the cluster. For MC/ServiceGuard Clusters, do the following: Halt ServiceGuard on the node the patch is to be installed on. Install this patch on that node. Restart ServiceGuard on that node. Patch needs to be installed on all nodes in the cluster. For customers using PHSS_26180 or later who have set MAX_CONFIGURED_PKGS to be a value greater than 60 packages, the following procedure must be used when upgrading to SG 11.14: Set AUTOSTART_CMCLD to 0 in /etc/rc.config.d/cmcluster Halt ServiceGuard (cmhaltnode) Upgrade this node to ServiceGuard or SG-OPS Edition 11.14 Install 11.14 SG and SG-OPS Patch PHSS_26056 or later to obtain > 60 package support on 11.14 Restart the node (cmrunnode) Modify /etc/rc.config.d/cmcluster to have the desired AUTOSTART_CMCLD value set Repeat for all nodes in the cluster. SR#: 8606215545 Cluster Object Manager patch PHSS_22175 or later must be installed in addition to PHSS_25915 or later in order to use the Administration features of ServiceGuard Manager version A.02.00. If installing PHSS_26674 or later on a ServiceGuard cluster with PHSS_26180 or earlier installed, do the following: Kill all EMS monitors (e.g., diskmond, mibmond, etc) on each node before starting ServiceGuard on that node. For quorum server A.01.00, visit http://www.software.hp.com for information on installation and documentation: Go to http://www.software.hp.com Click on "high availability" Click on "mc/serviceguard quorum server for hp-ux" Defect 25 (JAGae48414) listed for patch PHSS_27722 requires some consideration for the node timeout for some very specific customers. This fix introduces a change in behavior for ServiceGuard in the case where the system clock is not updated for a certain time period.  In this situation, the node will TOC if the system clock is not advancing for 5 node timeout periods. This change will make sure that whole cluster does not fail. And it will also make sure that Mission Critical applications are started on another node which does not exhibit the system clock problem. Large systems with higher number of CPUs/high amount of memory/large IO configurations are more susceptible to this phenomenon than small systems. It is recommended that for large systems a higher setting of the node timeout value from 5 to 8 seconds should be used. In addition a higher value of node timeout of 5 to 8seconds is also recommended for systems where any of the following symptoms have been seen before installation of this patch: a series of reconfigurations spaced by the node timeout value for no apparent reason & resulting in the same membership. or after installation of this patch following messages are seen in the syslog: Warning : Kernel ticks_since_boot is not advanced in the past xx seconds. or a system crash with following messages on console or in the crash dump: FAILURE : Kernel ticks_since_boot has not been advanced for xx seconds, which is greater than or equal to maximum allowable interval of XX seconds. This additional consideration is only required for defect 25 in PHSS_27722. This step is not required for any other fix in this or other patches. Defect 1 (JAGae67631) listed for patch PHSS_28849 requires the convert utility to be used manually on each node in the cluster after the patch is installed to correct the problem.  The following command should be used for running convert manually, assuming that the old configuration file is located at /etc/cmcluster/cmclconfig: # convert -f /etc/cmcluster/cmclconfig The cmrunnode command should then be reissued on each node. This is required only if symptoms are similar to Defect #1 listed in PHSS_28849. This step is not required for any other fix in this or other patches. 

As you can see, these Special Installation Instructions take some time to digest and then to implement. I suggest that you make time to read the Special Installation Instructions for the patches you are about to load. Otherwise, you may have a system (or a cluster as in the example above) that will not function properly.

If you select a patch that has dependencies, the ITRC will automatically include those dependent patches as part of your selection. You can unselect them, but unless you are sure you have the dependent patches already installed or available in a depot, the patch installation will fail because it cannot resolve dependencies . When you download a number of patches from the ITRC, you can either download them individually or as a collective package . You can choose the format of this package: zip , gzip , or tar . I have downloaded a collection of patches in tar format in this example:

 

 root@hpeos004[tmp]  ll patches[1].tar  -rw-r-----   1 root       sys        28827136 Sep  8 14:29 patches[1].tar root@hpeos004[tmp]  tar tvf patches[1].tar  r--r--r--  50/100   1780 Aug 29 18:31 2003 README_hp-ux rwxr-xr-x  50/100   4845 Sep  8 14:18 2003 create_depot_hp-ux_11 rw-r--r--  50/100  69803 Oct  4 08:40 2002 PHCO_27694 rw-r--r--  50/100 13134025 May 14 07:08 2003 PHSS_28676 rw-r--r--  50/100 253988 Jul 18 04:13 2002 PHCO_24777 rw-r--r--  50/100 183646 Apr 30 06:03 2003 PHCO_24839 rw-r--r--  50/100 5082689 May 15 06:41 2003 PHNE_28103 rw-r--r--  50/100 10088554 May 14 07:06 2003 PHSS_27873 root@hpeos004[tmp] 

Once I untar all these patches, I can run the script create_depot_hp-ux_11 . This will unshar the individual patches and swcopy them into a depot in my current directory called /tmp/depot unless I give the depot name on the command line. Here, I will use the script to copy all the patches into a depot called /depots/patches :

 

 root@hpeos004[tmp]  ./create_depot_hp-ux_11 -d /depots/patches  DEPOT: /depots/patches BUNDLE: BUNDLE TITLE: Patch Bundle UNSHAR: y PSF: depot.psf Expanding patch shar files... x - PHCO_27694.text x - PHCO_27694.depot [compressed] x - PHSS_28676.text x - PHSS_28676.depot [non-ascii] x - PHCO_24777.text x - PHCO_24777.depot [compressed] x - PHCO_24839.text x - PHCO_24839.depot [compressed] x - PHNE_28103.text x - PHNE_28103.depot [compressed] x - PHSS_27873.text x - PHSS_27873.depot [compressed] ...        * Beginning Analysis        * Session selections have been saved in the file          "/.sw/sessions/swverify.last".        * "hpeos004:/depots/patches":  There will be no attempt to mount          filesystems that appear in the filesystem table.        * Verification succeeded. NOTE:    More information may be found in the agent logfile using the          command "swjob -a log hpeos004-0045 @          hpeos004:/depots/patches". =======  09/25/03 15:26:09 BST  END swverify SESSION (non-interactive)          (jobid=hpeos004-0045) root@hpeos004[tmp] root@hpeos004[tmp]  swlist -l depot  # Initializing... # Target "hpeos004" has the following depot(s):   /depots/patches root@hpeos004[tmp] root@hpeos004[tmp]  swlist -l patch -s /depots/patches  # Initializing... # Contacting target "hpeos004"... # # Target:  hpeos004:/depots/patches # # PHCO_24777                    1.0            mountall cumulative patch. # PHCO_24777.UX-CORE               1.0               OS-Core.UX-CORE # PHCO_24839                    1.0            libpam_unix cumulative patch # PHCO_24839.CORE-SHLIBS           1.0               OS-Core.CORE-SHLIBS # PHCO_27694                    1.0            login(1) cumulative patch # PHCO_27694.UX-CORE               1.0               OS-Core.UX-CORE # PHNE_28103                    1.0            ONC/NFS General Release/Performance Patch # PHNE_28103.KEY-CORE                1.0                NFS.KEY-CORE # PHNE_28103.NFS-64ALIB              1.0                NFS.NFS-64ALIB # PHNE_28103.NFS-64SLIB              1.0                NFS.NFS-64SLIB # PHNE_28103.NFS-CLIENT              1.0                NFS.NFS-CLIENT # PHNE_28103.NFS-CORE                1.0                NFS.NFS-CORE # PHNE_28103.NFS-ENG-A-MAN           1.0                NFS.NFS-ENG-A-MAN # PHNE_28103.NFS-KRN                 1.0                NFS.NFS-KRN # PHNE_28103.NFS-KRN                 1.0                NFS.NFS-KRN # PHNE_28103.NFS-PRG                 1.0                NFS.NFS-PRG # PHNE_28103.NFS-SERVER              1.0                NFS.NFS-SERVER # PHNE_28103.NFS-SHLIBS              1.0                NFS.NFS-SHLIBS # PHNE_28103.NIS-CLIENT              1.0                NFS.NIS-CLIENT # PHNE_28103.NIS-CORE                1.0                NFS.NIS-CORE # PHNE_28103.NIS-SERVER              1.0                NFS.NIS-SERVER # PHNE_28103.NISPLUS-CORE            1.0                NFS.NISPLUS-CORE # PHSS_27873                      1.0             CDE Applications Periodic Patch # PHSS_27873.CDE-ENG-A-HELP          1.0                English Localized Help # PHSS_27873.CDE-ENG-A-MAN           1.0                CDE Man Pages # PHSS_27873.CDE-FONTS               1.0                CDE Font and Font Support # PHSS_27873.CDE-FRE-I-HELP          1.0                French Localized Help # PHSS_27873.CDE-GER-I-HELP          1.0                German Localized Help # PHSS_27873.CDE-HELP-RUN            1.0                CDE Help Runtime # PHSS_27873.CDE-ITA-I-HELP          1.0                Italian Localized Help # PHSS_27873.CDE-JPN-E-HELP          1.0                Japanese Localized Help # PHSS_27873.CDE-JPN-S-HELP         1.0               Japanese SJIS Localized Help # PHSS_27873.CDE-KOR-E-HELP          1.0                Korean Localized Help # PHSS_27873.CDE-LANGS               1.0                localized files # PHSS_27873.CDE-RUN                 1.0                CDE Runtime # PHSS_27873.CDE-SCH-H-HELP          1.0                Chinese Localized Help # PHSS_27873.CDE-SPA-I-HELP          1.0                Spanish Localized Help # PHSS_27873.CDE-SWE-I-HELP          1.0                Swedish Localized Help # PHSS_27873.CDE-TCH-B-HELP          1.0               Chinese Big5 Localized Help # PHSS_27873.CDE-TCH-E-HELP          1.0                Chinese Localized Help # PHSS_28676                      1.0             CDE Base Periodic Patch # PHSS_28676.CDE-DTTERM              1.0                CDE Terminal Emulator # PHSS_28676.CDE-ENG-A-MSG           1.0                English Localized Message Catalog # PHSS_28676.CDE-ITA-I-MSG           1.0                Italian Localized Message Catalog # PHSS_28676.CDE-MIN                 1.0                CDE Minimum Runtime # PHSS_28676.CDE-SCH-H-MSG           1.0                Chinese Localized Message Catalog # PHSS_28676.CDE-SHLIBS              1.0                CDE Shared Libraries # PHSS_28676.CDE-SWE-I-MSG           1.0                Swedish Localized Message Catalog # PHSS_28676.CDE-TCH-B-MSG           1.0                Chinese Big5 Localized Message Catalog # PHSS_28676.CDE-TT                  1.0                CDE Messaging root@hpeos004[tmp] 

The temptation here is to simply install the patches and worry about the Special Installation Instructions later. That is entirely up to you, but as you can see from our previous example, that can be a serious mistake. Some administrators have told me that when they have a large patch depot, it can be awkward to dig around the directory structure to find the text README file. My answer to this problem is simple ”on your own head be it! Oh, and have you ever thought about extracting the readme file using the swlist command?

 

 root@hpeos004[tmp]  swlist -s /depots/patches -a readme PHSS_28676  more  # Initializing... # Contacting target "hpeos004"... # # Target:  hpeos004:/depots/patches # # PHSS_28676 Patch Name: PHSS_28676 Patch Description: s700_800 11.11 CDE Base Periodic Patch Creation Date: 03/03/27 Post Date: 03/04/01 Hardware Platforms - OS Releases:         s700: 11.11         s800: 11.11 Products: N/A Filesets:         CDE.CDE-TCH-B-MSG,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP Standard input 

You have no excuses!



HP-UX CSE(c) Official Study Guide and Desk Reference
HP-UX CSE(c) Official Study Guide and Desk Reference
ISBN: N/A
EAN: N/A
Year: 2006
Pages: 434

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net