No, it's included by default when you backup the system tablespace, and hence included when you backup the database:
RMAN> backup tablespace system;
including current control file in backup set
including current SPFILE in backup set
If you are using the autobackup, then I don;t see any reason to use the 'include current controfile' clause.
Before closing this thread,please let me know if we can use this backup of current control file for below purpose
2)Incase system crash and to recover it
The situation is more complex, as I tried to explain in your other thread. But from what I understand, using the latest controlfile autobackup for RMAN duplicate will potentially fail, since the SCN in such controlfile is more likely going to be more advanced than the SCN of restored datafiles, hence requiring archivelogs during recovery past available archvielog backups. However, it depends on your environment, prerequisites, and how you perform the RMAN duplicate.
In terms of system crash and recovery, speaking of crash recovery, you require the current controlfile and online redo logs. Crash recovery is automatic and no RMAN restore or recovery is involved.
Thanks for providing an update.
so autobackup control file and current control file both can be used in restore and recovery including DBPIT recovery right?only the difference you say is,it is easy to restore an autobackup control file