Need clarification for cold backup and recovery

Question

Hello Everyone ..
I have much confusion on cold backup and recovery topic.
Already i posted a scanario regarding this and i want to know some clarity points to understand.
1. I had cold backup two days before
2. I am creating an object *(EMP)* and inserting some records then issue log switch continiously.
3. Manually i removed all physical files (datafiles , control files , log files , redolog files ...)
4. then i issued STARTUP FORCE MOUNT;
5. here i am getting error identifying control file.
6. cold backup two days before all files restored
6. then i issue recover database using backup controlfile until cancel;
7. i am trying to issue select * from emp; i am getting error
select * from emp
*ERROR at line 1:
ORA-00942: table or view does not existMy QUESTION IS
After cold backup finished , i created emp table ..
when restoring old back " There is no emp table"
*- then , can i recover emp table ? - If so , please explain about this ..*
Note : REF - LINK https://forums.oracle.com/forums/message.jspa?messageID=11056341#11056341
- Above link says what i did ? . In this thread i am asking concept & logic ..
please do NOT consider as "*DUPLICATE*"

Answer 1

When you recover the database using backup controlfile until cancel, you have to apply archived logs. Did you apply all of them?
If the create command was in the online redo, not yet archived, and you lost the online redo, then you won't have it. This is why you want to have redo multiplexed, it is a critical piece.
In some recovery scenarios, if you haven't lost the online redo, you need to specify those files as if they were archives.
It is normally easier to just be sure you have the latest controlfiles and let Oracle figure it out automatically (which is why you want to use online RMAN backups rather than cold backups). But yes, it is important to understand what is going on for different scenarios. I used to have manual standbys, and one of the disaster instruction sets explained to try to get online redo over to the standby to lose as few transactions as possible. That could still be useful for some snapshot hardware type scenarios, assuming the business is too cheap to do proper failovers.