Last updated on JUNE 12, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
- The end user sees 'ORA-04021: timeout occurred while waiting to lock object (DBD ERROR: OCIStmtExecute)'
- The ORA-04021 errors have never been displayed in the alert log or any trace files
- There is a CTAS (create table as select...) script running
- The objects are members of a cluster
- The system state dump shows that the resource holder that is blocking the activity (with an eXclusive lock on it (LockMode=X)) is an object in the recycle bin, Name=USER.BIN$KJkwX0JgCNgUx6MIQozYA==$0 (identified by the *.BIN$* prefix in the object name):
(the actual username has been replaced with USER in this example).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms