README VERSION : 1.1 README CREATION DATE : 2013-08-08 PATCH-ID : 5.1.134.000 PATCH NAME : VRTSdbed-5.1.134.000-SP1RP4_SLES10 BASE PACKAGE NAME : VRTSdbed BASE PACKAGE VERSION : 5.1.100.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sles10_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : Yes PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Release Notes for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Release Notes for uninstall instructions SPECIAL INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:5.1.134.000 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 SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:5.1.134.000 * INCIDENT NO: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. * INCIDENT NO:3238854 TRACKING ID:3247474 SYMPTOM: dbed_clonedb -S newdb -m /tmp/newdb -c 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. * INCIDENT NO: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. INCIDENTS FROM OLD PATCHES: --------------------------- NONE