Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - swaram92

Pages: [1]
« on: February 22, 2011, 11:30:49 AM »
Folks, since I got no response to my initial post, I am re-phrasing the question.

Our current strategy to recover a table (when its been mangled by a DBA,  batch or user), is to recover the RMAN backup pieces to an alternate machine (takes 4 hours for 160 G ).

Then we restore and recover the entire database to a  point-in-time (takes another 2.5 hours).

So by the time we are done exporting the table in question, its almost 7 hours!.

In this context I experimented with TSPITR and am quite comfortable with all parts of its working except where it imports the tablespace into the Recovery instance.

We can't rely on Flashback table since DDL change invalidates Flashback recovery

Please let me know if there is an alternate method to address my issue.

Thanks !

« on: February 10, 2011, 05:43:51 PM »
Hi experts, I am experimenting with TSPITR with Oracle 10g ( on HP-UX.

Though I have been successful with the tablespace recovery, I am not comfortable with the Recovery instance tablespace being subject to the import.

Is it possible to control/terminate  the phase of the recovery where the export from Auxiliary instance happens?  I prefer to do the export/import manually.


Ramesh Bala

Pages: [1]