RMAN-06067: RECOVER DATABASE required with a backup or created controlfile

Question

Hi,
DB:9.2.0.8
OS: AIX 5.3
I am restoring DB with until time(12/06/2012) for needed tablespaces.
I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
Restore of tablespaces are completed..
When recovery is going , failed with following error..
allocated channel: c7
channel c7: sid=22 devtype=SBT_TAPE
channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
allocated channel: c8
channel c8: sid=21 devtype=SBT_TAPE
channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET until clause
Starting recover at 23-06-2012 02:00:15
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/23/2012 03:36:57
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
RMAN>
Restore Script:
connect target /
connect catalog rmanc/recom@lgn_rmanc
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
allocate channel c9 type 'SBT_TAPE';
allocate channel c10 type 'SBT_TAPE';
allocate channel c11 type 'SBT_TAPE';
allocate channel c12 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
release channel c9;
release channel c10;
release channel c11;
release channel c12;
Recover Script:
connect catalog rmanc/recom@lgn_rmanc
connect target /
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
Any suggestion in this is helpful to me..
Thanks in advance,

Answer 1

Hello;
I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
2. Are you restoring to a different system?
3. How did you start the database ( NOMOUNT, MOUNT )
4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
5. Your command shows :
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
Meaning I don't use restore at all, in fact using restore may cause an issue.
SUMMARY : I don't see how this will work as is.
It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
This is an Incomplete Recovery. I believe I would rethink this completely.
Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
Once this is done I would decide how to get the data I need.
Or I would check for a daily export file and recover the tablespace data that way.
So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
Example
I'm recovering old tablespaces into a test system.
Here's how I'm not damaging my current production system.
I don't have an export from that date.
So take a step back and either rethink or give a few more details on how this is safe.
Best Regards
mseberg