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.300.100 REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol11_sparc (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : YES 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 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" PATCH ID:6.0.300.100 3018873 (3018869) On Solaris 11 update 1 fsadm command shows that the mountpoint is not a vxfs file system 3142142 (3079215) Oracle RAC Database creation failed with the Ora-00600 [ksfd_odmio1] error when Veritas ODM links. 3142252 (3142045) With Oracle 12c version, the Veritas Oracle Disk Manager (ODM) library causes a version mismatch on the RHEL6 platform. 3149270 (3149174) Veritas Oracle Disk Manager (ODM) clone shutdown fails with the ORA-03113: end-of-file on communication channel error. 3241794 (3101418) The current time returned by the operating system (Oracle error code ORA-01513) during Oracle startup is invalid. PATCH ID:6.0.300.000 3018873 (3018869) On Solaris 11 update 1 fsadm command shows that the mountpoint is not a vxfs file system 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. PATCH ID:6.0.300.100 * INCIDENT NO:3018873 TRACKING ID:3018869 SYMPTOM: fsadm command shows that the mountpoint is not a vxfs file system DESCRIPTION: The Solaris11 update1 has some changes in function fstatvfs() [VFS layer] which breaks VxFS's previous assumptions. The statvfs.f_basetype gets populated with some garbage value instead of "vxfs". So, during the fsadm, when we check for the file system type, the check fails and so we get the error. RESOLUTION: Made changes to fetch correct value for fstype using OS provided API's so that the statvfs.f_basetype field gets valid i.e. "vxfs" value. * 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. PATCH ID:6.0.300.000 * INCIDENT NO:3018873 TRACKING ID:3018869 SYMPTOM: fsadm command shows that the mountpoint is not a vxfs file system DESCRIPTION: The Solaris11 update1 has some changes in function fstatvfs() [VFS layer] which breaks VxFS's previous assumptions. The statvfs.f_basetype gets populated with some garbage value instead of "vxfs". So, during the fsadm, when we check for the file system type, the check fails and so we get the error. RESOLUTION: Made changes to fetch correct value for fstype using OS provided API's so that the statvfs.f_basetype field gets valid i.e. "vxfs" value. INCIDENTS FROM OLD PATCHES: --------------------------- NONE