12.2 E-Business Technology Code Level Checker (ETCC) Recommended Patch 23745950 Fails With A Conflict On 23309651, And After Rollback Database Fails To Start With Error 'ORA-04024 self-deadlock Detected'
(Doc ID 2218681.1)
Last updated on JANUARY 09, 2017
Applies to:Oracle Applications Technology Stack - Version 12.1.3 and later
Oracle Applications DBA - Version 12.1.3 and later
Information in this document applies to any platform.
E-Business Suite 12.1.3 Applications DBA, Upgrade related issues
After running the EBS Codelevel Checker recommendation summary before upgrading to 12.2.5, the codelevel checker identified several database patches to be applied.
All patches were successfully applied without any warnings, except <Patch 23745950>.
During the install process for MLR DB <Patch 23745950>, a conflict was identified with existing MLR <Patch 23309651>.
To resolve the conflict MLR <Patch 23309651> was rolled back in order continue with MLR <Patch 23745950>.
However after the rollback of MLR <Patch 23309651> and the completion of database MLR <Patch 23745950>, the following error occurs in database alert log and database cannot be re-started:
'ORA-04024: self-deadlock detected while trying to mutex pin cursor 0x0CCC30000'
The issue can be reproduced at will with the following steps:
1. Apply patch 23745950.
2. Receive message warning of a conflict identified with existing patch 23309651.
3. Rollback patch 23309651 and continue with application of patch 23745950.
4. Once the patch application is successfully confirmed, attempt to restart database.
5. Error is encountered and database cannot be restarted.
Due to this issue users cannot apply the recommended database patch and comply with the Codelevel Checker requirements, as the rollback causes database crash.
This will also effect future stages of the EBS upgrade project and the associated application functionality.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!