README VERSION : 1.1 README CREATION DATE : 2014-04-08 PATCH-ID : 6.0.500.000 PATCH NAME : VRTSodm 6.0.500.000 BASE PACKAGE NAME : VRTSodm BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : 6.0.400.000 REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sles11_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : Yes PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install guide for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install guide for uninstall instructions SPECIAL INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:6.0.500.000 3322294 (3323866) Some ODM operations may fail with "ODM ERROR V-41-4-1-328-22 Invalid argument" 3369038 (3349649) The Oracle Disk Manager (ODM) module fails to load on RHEL6.5 PATCH ID:6.0.400.000 3241794 (3101418) The current time returned by the operating system (Oracle error code ORA-01513) during Oracle startup is invalid. 3248960 (3248955) Support for SLES11 SP3 is now added for ODM. 3271693 (3268931) Support for SLES 11 SP3 is added. PATCH ID:6.0.300.100 3142142 (3079215) Oracle RAC Database creation failed with Ora-00600 [ksfd_odmio1] error when Veritas ODM linked. 3142252 (3142045) With Oracle 12c version ,ODM version mismatch issue observed. 3149270 (3149174) ODM clone shutdown is fails with error "ORA-03113: end-of-file on communication channel" 3241794 (3101418) Oracle during startup displays ORA-01513 errors. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:6.0.500.000 * INCIDENT NO:3322294 TRACKING ID:3323866 SYMPTOM: Some ODM operations may fail with the following error: ODM ERROR V-41-4-1-328-22 Invalid argument DESCRIPTION: On systems having heavy database activity using ODM some operations may fail an error. This is a corner case and it occurs when a new task enters in ODM. To avoid deadlocks ODM maintains two lists of tasks viz. hold list and deny list. All the active tasks are maintained in the hold list and the task that are being exited from ODM are stored in the deny list. The error is returned when the ODM PID structure gets re-used for a PID that is still being exited from the ODM and is there in the deny list in that case ODM don't allow the task to enter in the ODM and above error is returned. RESOLUTION: The code is modified such as to add an extra check while adding a new task in ODM to avoid returning the error in such scenarios. * INCIDENT NO:3369038 TRACKING ID:3349649 SYMPTOM: Oracle Disk Manager (ODM) module fails to load on RHEL6.5 with the following system log error message: kernel: vxodm: disagrees about version of symbol putname kernel: vxodm: disagrees about version of symbol getname DESCRIPTION: In RHEL6.5, the kernel interfaces for AgetnameA and AputnameA used by VxFS have changed. RESOLUTION: The code is modified to use the latest definitions of AgetnameA and AputnameA kernel interfaces. PATCH ID:6.0.400.000 * INCIDENT NO:3241794 TRACKING ID:3101418 SYMPTOM: The invalid current time is returned by the operating system (Oracle error code ORA-01513) during Oracle startup. DESCRIPTION: Oracle intercepts calls to the localtime_r() function as it is not asynchronous signal safe. They do not support any client library to spawn a thread and call the localtime_r() function. The localtime_r() function is called from the feature_tracking library as a part of the odm_discover() function in VRTSodm. RESOLUTION: The code is modified so that it does not spawn the thread and call the localtime_r() function, while feature_tracking. * INCIDENT NO:3248960 TRACKING ID:3248955 SYMPTOM: Support for SLES11 SP3 was not present on ODM DESCRIPTION: Support for SLES11 SP3 was not present on ODM RESOLUTION: Support for SLES11 SP3 is now added for ODM. * INCIDENT NO:3271693 TRACKING ID:3268931 SYMPTOM: Module load failing on sles11 sp2/sp3, DESCRIPTION: sles11 sp2 having higher kernel version than sp3, module installation failing since our installer script checks for version near to highest version on the target machine, if unable to load highest version module, then give up. RESOLUTION: Now if our installer is unable to load highest kernel version(incompatible) matching to target, it checks for lower version also until it got installed any module or exhausted the list of incompatible modules. This will work for all linux distros. PATCH ID:6.0.300.100 * INCIDENT NO:3142142 TRACKING ID:3079215 SYMPTOM: Oracle RAC Database creation failed with Ora-00600 [ksfd_odmio1] error when Veritas ODM linked. DESCRIPTION: Earlier ODM interface provides a context pointer which is returned to oracle by odm_init() and then passed back to ODM by oracle with each interface call, here ODM interface just keeping track of whether we are running oracle (>10GR2 or not) In Oracle 12, introduced/started using multiple contexts from the same process, but currently our implementation of odm library is not set up multithreaded which doesn't hadle this which causing the EBADF(Bad file descriptor). RESOLUTION: Introduced new changes to support multiple contexts per process. * INCIDENT NO:3142252 TRACKING ID:3142045 SYMPTOM: With Oracle 12c version, Veritas ODM library give version mismatch issue DESCRIPTION: Each process/task, calling ODM ioctl, has exit hook which scan VMA of process/task for valid libodm library. VMA of process/task contains libodm.so text section. Exit hook compares the VMA's libodm library names with hard-coded library names such as libodm9.so, libodm10.so etc. Some of the new Oracle versions might have conflicting hard-coded names with its predecessor, such as 12c. And the conflicting names fail the check on the existence of libodm in VMA. RESOLUTION: To avoid this issue, library name comparison is now done with valid 'libodm' pattern instead of hard-coded library name. * INCIDENT NO:3149270 TRACKING ID:3149174 SYMPTOM: ODM clone shutdown is failing with error "ORA-03113: end-of-file on communication channel" DESCRIPTION: odm_fini() which generally releases the memory allocated for the context and any other memory structure that have not yet been freed, can be called multiple times.Here odm_fini() being called twice with the same context which causes the problem RESOLUTION: Before freeing, clear the pid field of the context structure to avoid double freeing if odm_fini is called by mistake again with same context * INCIDENT NO:3241794 TRACKING ID:3101418 SYMPTOM: The invalid current time is returned by the operating system (Oracle error code ORA-01513) during Oracle startup. DESCRIPTION: Oracle intercepts calls to the localtime_r() function as it is not asynchronous signal safe. They do not support any client library to spawn a thread and call the localtime_r() function. The localtime_r() function is called from the feature_tracking library as a part of the odm_discover() function in VRTSodm. RESOLUTION: The code is modified so that it does not spawn the thread and call the localtime_r() function, while feature_tracking. INCIDENTS FROM OLD PATCHES: --------------------------- NONE