24.12.2012 Views

Backing Up Oracle - Computing at Cornell

Backing Up Oracle - Computing at Cornell

Backing Up Oracle - Computing at Cornell

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Some hours after the successful recover, the failed disk went online again.<br />

We found not only the suspected d<strong>at</strong>afiles, control file, and log archive<br />

directory, but also redo log files in the /u02/orad<strong>at</strong>a file system and a d<strong>at</strong>afile<br />

belonging to a temporary tablespace.<br />

We queried the d<strong>at</strong>abase and recognized th<strong>at</strong> only every second member of<br />

each group was INVALID, but after a log switch they were usable again:<br />

8.3.3 Incomplete recovery<br />

This example shows how to restore and recovery a d<strong>at</strong>abase to a specific<br />

point in time.<br />

Incomplete recovery is sometimes also d<strong>at</strong>abase point in time recovery or<br />

DBPITR called.<br />

To test an incomplete recovery, we did these steps:<br />

We started the <strong>Oracle</strong> instance berlin.<br />

We performed a consistent whole d<strong>at</strong>abase backup with tag = ‘berlin<br />

offline 20010326.0925’.<br />

We cre<strong>at</strong>ed new tables and inserted some rows.<br />

We archived the redo log files.<br />

We stopped the <strong>Oracle</strong> instance berlin by a shutdown abort.<br />

We removed all control files.<br />

112 <strong>Backing</strong> <strong>Up</strong> <strong>Oracle</strong> using Tivoli Storage Management

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!