I'm sorry if I got it wrong. From what I understand you've got a physical standby which has unresolvable archive gap ? If that's the case refer to:
Steps to perform for Rolling forward a standby database using RMAN Incremental Backup. (Doc ID 836986.1)
IF you want to update the Standby with an SCN based incremental backup, you need to know the SCN on the Standby.
Query v$DATABASE on the Standby for the SCN and run a fresh incremental backup for SCN-1 onwards.
Note : An SCN based incremental backup is ONLY for updating a Standby. It cannot be part of a backup / recovery strategy for a Primary.
Hemant K Chitale
I guess u haven't understood my question.My scenario is my restoration will take around 5 to 6 hours using the backup.Once the restoration is complete i can query the SCN from v$DATABASE on the Standby,but i don't want to wait till the restoration gets complete.If i know the SCN in the backup i can fire the SCN based incremental backup in production database parallely when the restoration is in progress.
List backup is not showing the SCN since control file in not included in my backup because we use recover database using backup controlfile until cancel statement to recover the logs and the controlfile type is backup.
I hope u understand my scenario more clearly.