README VERSION : 1.1 README CREATION DATE : 2012-09-24 PATCH-ID : 142632-06 PATCH NAME : VRTSdbed 5.1 SP1RP3 BASE PACKAGE NAME : Veritas Storage Foundation for Oracle from Symantec 142632-06SP1RP3(patch-6) BASE PACKAGE VERSION : VRTSdbed 5.1SP1 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol10_x86 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer the release notes for installation instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer the release notes for un-installation instructions. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 2848176 (2816482) vxdbd memory leak in build_function_header() 2848193 (2664050) vxdbd coredumps in build_function_header on malloc failure 2848204 (2664794) vxdbd sigseg in strcpy from dbed_ul_print_valist 2915205 (1957142) reverse_resync_abort and reverse_resync_commit fails SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:142632-06 * INCIDENT NO:2848176 TRACKING ID:2816482 SYMPTOM: memory consumed by vxdbd continues to increase with time, even when the daemon is totally idle. DESCRIPTION: After a few minutes of running vxdbd , 2 memory leaks are observed in the code. This seems to occur even if the vxdbd is idle RESOLUTION: free the memory allocated in the above two scenarios. * INCIDENT NO:2848193 TRACKING ID:2664050 SYMPTOM: vxdbd core dump after running for about 5 hours DESCRIPTION: VXDBD was running fine for about 5 hours. (10:15 to 15:15) VXDBD calls "vxdctl -c mode" every minute to figure out if its the MASTER node or not If MASTER, the code tries to run scheduled jobs. After running for a few hours, malloc fails at this point and the return value is not checked leading to a failure. RESOLUTION: Check for the return value of malloc() and bail out if memory not allocated. * INCIDENT NO:2848204 TRACKING ID:2664794 SYMPTOM: Sometime after startup vxdbd process is core dumping due to segmentation fault. DESCRIPTION: In the function dbed_ul_print_valist() the return value from malloc() is not checked leading to the dailure. RESOLUTION: Added a check for malloc() failure in dbed_ul_print_valist(). * INCIDENT NO:2915205 TRACKING ID:1957142 SYMPTOM: Sometimes reverse_resync_abort and reverse_resync_commit operation fail with an error similar to SFORA dbed_vmsnap ERROR V-81-3004 An error occurred while shutting down the database instance. DESCRIPTION: Currently the database is shutdown within the script as "SHUTDOWN NORMAL", In NORMAL shutdown the Oracle database would wait for all connections to exit or complete any pending tasks. This is not really necessary since at times the connections are open with no activity. This causes the operation to stall for sometime before eventually quitting with an error. RESOLUTION: The Shutdown is done now, using SHUTDOWN IMMIDIATE. INCIDENTS FROM OLD PATCHES: --------------------------- Patch Id::142632-05 * Incident no::2390388 Tracking ID ::2395192 Symptom::The vxdbd daemon consumes excessive CPU. Description::The vxdbd daemon listens on TCP port 3233 for client connections. When a client connects, the server loops by design in vxdbd_handle_connection(). However, this looping is eventually supposed to end. In this case, for some connections and under some unknown conditions, it doesn't. For whatever reason, vxdbd threads are stuck in this loop continuing to read and write to these sockets while the number of looping threads grows over time. Meanwhile, the sockets are in an IDLE state which means the client is no longer active on the connection. Resolution::The read_n function was incorrectly returning a positive value in case of error, which caused its caller to loop indefinitely. The function was fixed to correctly return a negative value on error.