Patch-ID# 145644-07

23172046 status message for encryption refers to HA-MySQL agent
25247140 stop script reports error message on console
25247165 rolechanger resource must become IPv6-compliant
25247193 agent must use a FIPS 140-compliant OpenSSL version
25289869 agent should support downloadable 64-bit binaries
 
(from 145644-06)
 
20565562 PostgreSQL agent needs to take FIPS 140 activation setting into account
21872176 PostgreSQL agent must not use getent hosts
22165634 problem with HA-PostgreSQL
22263693 register script creates wrong dependencies for scalable mountpoints
 
(from 145644-05)
 
15700470 register scripts need to define resource_offline_restart dependencies for HAStoragePlus
 
(from 145644-04)
 
16216625 validation fails if LD_LIBERARY_PATH is set
 
(from 145644-03)
 
        This revision accumulates feature point patch 150034-01 into OSC 3.3 U2.
 
(from 145644-02)
 
        This revision accumulates feature point patch 146162-01.
 
        This revision was planned in anticipation of including into update 1
        new features expected to be in the above feature point patch.  In
        this case, that particular feature point patch ended up not being
        targeted for such changes.  It is not necessary to install this
        revision to a system having the prior 145644-01 revision.
 
(from 145644-01)
 
6982258 PostgreSQL agent should support version 9.x
 
(from 146162-01)
 
        This revision is effectively a copy of the 145644-01 sustaining patch.
 
(from 150034-01)
 
15703164 the password for the database monitor user should not be stored in clear text
15704895 problem with HA-PostgreSQL
16021116 PostgreSQL agent should be part of 4.2

--------------------------------
 
There are three (3) possible procedures for installing patches on Oracle
Solaris Cluster. The proper method to use and any additional instructions
for this patch are specified below in the "Special Install Instructions"
section.
 
Refer to the chapter entitled "Patching Oracle Solaris Cluster Software and
Firmware" in the "Oracle Solaris Cluster System Administration Guide" for a
description of the different install processes and instructions on how to
install Oracle Solaris Cluster 3.3 patches.
 
Refer to the man pages for instructions on using 'patchadd' and 'patchrm'
commands provided with Oracle Solaris, to install and remove patches.

-----------------------------
 
NOTE 1:  Install this patch using one of the following patch install
         procedures found in the "Patching Oracle Software and Firmware"
         chapter of the "Oracle Solaris Cluster System Administration Guide:"
 
         * Non Rebooting Patch
         * Rebooting Patch (Node)
         * Rebooting Patch (Cluster and Firmware)
 
NOTE 2:  Revision -02 delivers features introduced during update 1.
 
NOTE 3:  Revision -04 adds the feature to hide and encrypt the password for
         the database monitoring user.
 
         If you do not want the password store in human readable form, do
         the following:
 
         Do not store the password in the configuration file.
 
         For the database preparation call the database preparation script
         as the PostgreSQL user in the following form:
 
         $ ksh /opt/SUNWscPostgreSQL/util/pgs_db_prep -f <config file> -e
 
         You will be prompted for the password.
 
         Do this on the node where you installed and run PostgreSQL.
 
         Encrypt the password:
 
         On all nodes/zones to run PostgreSQL call the following script
         as root user:
 
         # ksh /opt/SUNWscPostgreSQL/util/pgs_register -f <config file> -e
 
         You will be prompted for the password.  Use the same password you
         provided during the database preparation on all nodes.
 
         After doing this on all nodes/zones, you are ready to register the
         PostgreSQL resource on one node with:
 
         # ksh /opt/SUNWscPostgreSQL/util/pgs_register -f <config file>
 
NOTE 4:  Revision -04 delivers features introduced during update 2.
 
NOTE 5:  Starting with patch revision -06 you need to run password encryption
         on one node only.
 
         The encryption is:
 
         # ksh /opt/SUNWscPostgreSQL/util/pgs_register -f <config file> -e
 
         The type of zone you must run the encryption in depends on the zone
         you are planning your data service for.
 
         For a global zone, run it in on one global zone.
         For a zone cluster, run it on one node of the zone cluster.
         For a zone node, run it on one global zone.