RMAN Duplicate hang on error: WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!

Problem:

I was trying to duplicate a 19c database from an RMAN backup, but it was hanging at this final stage of opening the cloned DB in resetlogs mode:

Analysis:

When checked the alertlog I found the following messages in the alertlog:

2022-03-21T13:14:26.588816+00:00
>>> WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! pid=58
System State dumped to trace file /oracle/19.5/diag/rdbms/uat3/uat3/trace/UAT3_p00e_5888.trc
2022-03-21T13:14:27.941400+00:00
TT03 (PID:5858): Sleep 160 seconds and then try to clear SRLs in 8 time(s)
2022-03-21T13:17:07.941846+00:00
TT03 (PID:5858): Sleep 320 seconds and then try to clear SRLs in 9 time(s)
2022-03-21T13:18:01.355711+00:00
********************  WARNING **************************
The errors during server control file autobackup are not
fatal, as it is attempted after sucessful completion of
the command. However, it is recomended to take an RMAN
control file backup as soon as possible because the
autobackup failed with the following error:
ORA-00237: snapshot operation disallowed: control file newly created

********************  END OF WARNING *******************

 After a long search, I figured out that it's Bug 30931981 which impacts 19c and was fixed in 21c, also I figured that I'm having more patches installed on the target cloned target DB ORACLE_HOME compared to the ones installed on the source DB ORACLE_HOME which I'm cloning from.

Solution:

Permanent: Apply patch 30931981

Workaround: Make sure the target "cloned DB" ORACLE HOME is having same patches installed as similar to the source DB you are cloning from.