On occasion, it is necessary to restore just one tablespace in a database to a Point-In-Time. This short blog will describe just how easy it is with just four steps.
- Take the tablespace offline:
alter tablespace <tablespace_name> offline;
- Issue the restore command from an RMAN prompt. This step may take a bit of time, depending on how large the backup set is and how large the tablespace is. Also, this step will actually start an “Auxiliary” database up, restore the datafile to it and then copy it to the database. So, do not panic when you see and database startup and stop.
restore tablespace <tablespace_name> until time "to_date('19-APR-2019 06:30:00','DD-MON-YYYY:HH24:MI:SS')";
- After the restore is completed, a “Recover” needs to be issued. Depending on how many archive logs it has to roll through will determine how long this step will take.
recover tablespace <tablespace_name> until time = "to_date('12-APR-2019 07:30:00','DD-MON-YYYY:HH24:MI:SS')" auxiliary destination '<Disk Location>';
- Finally, the tablespace can be brought back online.
alter tablespace <tablespace_name> online;
And that’s how easy it is to restore a single tablespace to a point in time using RMAN, did it work for you?
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.