RE: RMAN TSPITR Puzzle
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 27 May 2011 09:20:58 -0700
Hi Mark,
No, I didn't run a RESTORE command. I thought that seemed unusual too, but
this is how fully automated TSPITR is supposed to work (this was my first time
trying it) - you just run the RECOVER TABLESPACE command and RMAN automatically
creates an auxiliary instance, allocates auxiliary channels, restores the
required datafiles, recovers them, then exports & imports the metadata for the
transportable tablespaces to transfer them from the auxiliary back to the
target DB.
After several hours of research and troubleshooting, it turns out that my
problem isn't a bug or an unknown issue - it's clearly documented here:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/ostspitr.htm#i1006222
"The control file must have been backed up before the desired TSPITR time."
I just don't understand why that is. It seems backwards to me. I would think
you would need the control file from after the desired TSPITR time in order for
the control file to be aware of all the required backup pieces, but apparently
I'm wrong. I'm going to do some more research and testing until I fully
understand it. Another list member has sent me some ideas but I haven't had a
chance to review and test them yet. Once I do, I'll post my understanding of
the issue since it seems that I'm not the only one that is confused by this.
Thanks,
Brandon
From: Bobak, Mark [mailto:Mark.Bobak@xxxxxxxxxxxx]
You only show the 'RECOVER' command. Did you do an explicit 'RESTORE
TABLESPACE' before the 'RECOVER TABLESPACE'? Did you have a corresponding
'until sequence 647' clause specified for the 'RESTORE'?
________________________________
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
Other related posts:
