ORA-00054: resource busy and acquire with NOWAIT specified

I encounter this scenario back late last year when our database support teams wanted to duplicate a table and drop the corrupted original copy. This occurs when trying to acquire a table lock when the table already has one of a number of different lock present within that table. So our approach was to try the ff: Re-run/Retry the DB name change when the database is idle and when all apllications are down; i.e. during the maintenance window with all end-users locked-out; and Kill the sessions that are preventing the exclusive lock.

Recommendation from the compiled Internet resource to come-up with this idea was the following: