* * * READ ME * * *
                * * * Database Edition 5.1 SP1 RP3 * * *
                         * * * P-patch 1 * * *
                         Patch Date: 2019-03-25


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Database Edition 5.1 SP1 RP3 P-patch 1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
HP-UX 11i v3 (11.31)


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSdbed


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation 5.1 SP1
   * Veritas Storage Foundation Cluster File System 5.1 SP1
   * Veritas Storage Foundation HA 5.1 SP1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: PHCO_44786
* 3965995 (3967230) Oracle 12c support.
Patch ID: PHCO_43528
* 3237796 (3239626) [51SP1RP4] dbed_vmclonedb fails if primary database has multiple archive_dests set.
* 3238854 (3247474) dbed_clonedb failed for ORA-[0-9][0-9][0-9][0-9][0-9] error check in "vxdba_sqllib.sh".
* 3241900 (3244283) dbed_vmsnap -o snapshot fails on slave node of SFRAC cluster
* 3243038 (3244753) Flashsnap fails if hostname is longer than 8 characters.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: PHCO_44786

* 3965995 (Tracking ID: 3967230)

SYMPTOM:
Storage Foundation for Databases (SFDB) tools did not support Oracle 12c.

DESCRIPTION:
Storage Foundation for Databases (SFDB) tools did not support Oracle 12c.

RESOLUTION:
This patch provides support for Oracle 12c with the Storage Foundation for Databases (SFDB) tools.

Patch ID: PHCO_43528

* 3237796 (Tracking ID: 3239626)

SYMPTOM:
dbed_vmclonedb fails if primary database has multiple archive_dests 
set.

DESCRIPTION:
The code checked and processed only 5 log_archive_dest_n. These 
log_archive_dest_n are 
commented out and finally a single log_archive_dest is added to the clone_pfile. 
So if more than 5 were 
created it led to the clone pfile being incorrectly configured - all 
log_archive_dest_n beyond 5 were not 
commented and that along with the log_archive_dest parameter led to the clone 
database not coming up.

RESOLUTION:
Process all the log_archive_dest_n parameters from 1 to 31 and 
handle the same in the clone 
database's pfile.

* 3238854 (Tracking ID: 3247474)

SYMPTOM:
dbed_clonedb -S newdb -m /tmp/newdb -c <checkpoint_name> fails with an 
error similar to 
...
An error occurred while reconfiguring Oracle instance 'newdb'.
Log file is at /tmp/oralog.out.6742.
...

DESCRIPTION:
Certain deprecated parameters , for eg. 'log_archive_start' in the 
init 
file raise an Oracle warning ORA-32004 which is not getting ignored when 
starting up 
the clone database and is treated as an error in dbed_clondb script.

RESOLUTION:
Ignore the code ORA-32004 when starting up the clone database.

* 3241900 (Tracking ID: 3244283)

SYMPTOM:
dbed_vmsnap -o snapshot sometimes fails with the following error if the 
setup has volume-sets
SFORA vxsnapadm ERROR V-81-5907 lstat() /dev/vx/rdsk/dg/SNAP_archvol failed (No 
such file or directory).
SFORA dbed_vmsnap ERROR V-81-5593 fsck /dev/vx/dsk/dg/SNAP_archvol failed.
SFORA vxsnapadm ERROR V-81-5545 Could not exec mount /for 
/tmp/dbed_vmclonedb.27709/snap_arch/sfaedb.27709/snap_arch/sfaedb on 
/dev/vx/dsk/dg/SNAP_archvol.
SFORA dbed_vmsnap ERROR V-81-5595 mount device /dev/vx/dsk/dg/SNAP_archvol 
failed.
SFORA dbed_vmsnap ERROR V-81-5666 snapback  datavol archvol failed.
SFORA dbed_vmsnap ERROR V-81-5667 Please contact system administrators.

DESCRIPTION:
Once the snapshot is done, the member snapshot volumes get created 
and sometimes it takes a 
couple of seconds for the parent snapshot volume to be created in the device 
folder /dev/vx/dsk or 
/dev/vx/rdsk this leads to the failure when an fsck is attempted after the 
snapshot operation with the 
dbed_vmsnap script.

RESOLUTION:
Retry the fsck operations with a delay of 2 seconds on every failure 
before proceeding 
furthur.

* 3243038 (Tracking ID: 3244753)

SYMPTOM:
DBED operation fail if the hostname is greater than 8 characters in length on hpux system. For example sfua_db_config 
fails with the following error
...
SFORA /opt/VRTS/bin/sfua_db_config ERROR V-81-8911 chgrp returned error on <hostxxxx>
VXDBA_PRODUCT exec_remote ERROR V-81-7700 Can not connect to the vxdbd. It might be down. Check the status and restart it if it 
is not up.

DESCRIPTION:
The DBED scripts make use of uname -n to get the current hostname. This returns only the first 8 characters of the 
hostname, and hence DBED tries to perform operations on an incorrect host.

RESOLUTION:
Changed the DBED scripts to make use of /usr/bin/hostname' instead of 'uname -n'



INSTALLING THE PATCH
--------------------
Installing the 5.1 SP1RP3P1 VRTSdbed Command Patch:

1) 5.1 SP1RP3 VRTSdbed command patch must be installed before applying this patch.

2) To verify the VERITAS dbed patch installed on the machine, enter:

    # swlist -l product | egrep -i 'VRTSdbed'
    
      PHCO_43528                    1.0            VRTS 5.1 SP1RP3 VRTSdbed Command Patch
        VRTSdbed                      5.1.100.000    Veritas Storage Foundation for Oracle by Symantec

3)To install the patches, enter the following command:

    # swinstall -s <patch_directory>  PHCO_44786

4) To verify this patch installed on the machine, enter:

    # swlist -l product | egrep -i 'PHCO_44786'

      PHCO_44786                    1.0            VRTS 5.1 SP1RP3P1 VRTSdbed Command Patch


REMOVING THE PATCH
------------------
To remove the patch, enter the following command:

    # swremove PHCO_44786


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE