recover database using backup controlfile until cancel;
<enter> Then directly write cancel <enter> and then try to open using resetlogs.
If you still get ORA-01110, then you need to recover.
Again use recover database using backup controlfile until cancel;
But this time supply archivelogs or redologs (if they are containing the changes that are required to be applied for the recovery)
I already did it. It is still asking for archivelogs which does not exist on production. I have applied all the latest once.
Extract from alert log
Media Recovery Log /archive/winsdb/2_27956_767727243.arc
Fri Nov 25 14:09:02 2016
Media Recovery Log /archive/winsdb/2_27957_767727243.arc
Fri Nov 25 14:10:33 2016
Media Recovery Log /archive/winsdb/2_27958_767727243.arc
Fri Nov 25 14:12:10 2016
Media Recovery Log /archive/winsdb/2_27959_767727243.arc
Fri Nov 25 14:13:46 2016
Media Recovery Log /archive/winsdb/2_27960_767727243.arc
Fri Nov 25 14:13:46 2016
Errors with log /archive/winsdb/2_27960_767727243.arc
Errors in file /opt/app/oracle/diag/rdbms/winsdb/WINSDB2/trace/WINSDB2_pr00_14991.trc:
ORA-00308: cannot open archived log '/archive/winsdb/2_27960_767727243.arc'
ORA-17503: ksfdopn:4 Failed to open file /archive/winsdb/2_27960_767727243.arc
ORA-17500: ODM err:File does not exist
Fri Nov 25 14:14:23 2016
ORA-279 signalled during: alter database recover automatic using backup controlfile until cancel...
Try the "redologs" for the recovery.
I mean when the recovery will ask archives, give redologs to it. (the correct redolog ofcourse, try redologs one by one)