Is this method of Cloning old ?

Question

DB version:10.2.0.4
This is what we do to Clone our large Production DB(4 TB). Because of some practical issues, we don't do it in one day.
After the DUPLICATE .... DORECOVER command. We keep the aux db in mount mode and keep applying arch logs generated at primary DB.
This is what we do currently. Is this method of Cloning Old ?
=== Start====
After the pre-requisite setup of tnsnames, listener.ora, password file , pfile
Step1. Take the Full backup of Primary DB
step2. Creation of stanby control file using -- at primary DB
run {
allocate channel d1 TYPE DISK connect 'sys/pass@mydb'  FORMAT   '/u02/bkp/mydb_cntr_%U.rmbk';
backup current controlfile for standby;
     }Step3.
Connect to Primary DB using
rman target sys/pass@myproddb catalog rman/pass@rmancat AUXILIARY/and run
duplicate target database for standby dorecover;Step4.
Now at standby DB we issue the following command for Arch redo log apply.
recover automatic standby database;Step5.
After applying all the archivedlogs we issue
alter database recover managed standby database finish force;Don't know exactly what this is for.
Step6.
alter database commit to switchover to primary;==== End ===

Answer 1

No, it's not
As the clone process takes long time for large databases, it's the best practice to create a standby db and apply archived redo log files that were generated during the clone process