Oracle Alert log will have the following entries:
Errors in file
ORA-00600: internal error code, arguments: [ksfd_odmio1], [0x7F5FBBF8FF70],
[0x7F5FBBF8FF98], [1], [ODM ERROR V-41-4-1-354-22 Invalid argument], [], [],
[],
[], [], [], []
...
When the index creation process gets a SIGALARM during a clone() system call, it causes the clone() call to back out.
But this backing out of the partially-done clone() call confuses ODM’s process-exit-detection mechanism,
causing it to think that the process calling clone() is the one being torn down.
Hence, ODM removes its kernel structures for that process and whenever it tries it the next to issue an I/O, it results in this error.
A supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix.
Veritas Technologies LLC currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Applies To
Systems running Oracle (both standalone or RAC) with VRTSodm 6.x on RHEL5/6 or SLES 11
error V-41-4-1-354-22.
In this case, the customer tried creating INDEX of large number of BLOB (100k+ Binary Large Object) which failed with above ODM error.