I have a previous
article available here
that explains about ORA-00054 and the reason of this error, and alto the
enhancement starting 12c to avoid this error. In this article I would further
explain ORA-00054 and how to use an initialization parameter DDL_LOCK_TIMEOUT
to avoid this error. Instead of returning this error because of a lock on the
object, your DDL would keep waiting for the locks to be released and get
executed automatically when object is available for the DDL operation.
Oracle Installation guides, Linux Administration tips for DBAs, Performance Tuning tips, Disaster Recovery, RMAN, Dataguard and ORA errors solutions.
No contents from my website can be published anywhere else without my permission. Test every solution before implementing in the production environment.
Sunday, June 28, 2020
Sunday, June 7, 2020
ASM Disks not Reachable After Reboot - Manually Loading ASM Driver
After a system reboot if
you see ASM disks are not available, and scanning ASM disk returns “Unable to
instantiate disk”, as follows, it could be because oracleasm driver was not
loaded and hence ASM did not work as expected. As a result, ASM disks will not be visible to ASM instance and ASM diskgroups would not mounted. Following is the
example output of if you execute “oracleasm scandisks” command.