Hi,

9.2.0.4

I am currently testing backup and recovery of this version prior to going live with the migration.

I do a full hot backup each night with RMAN using the following....

run {
# backup the database to disk
allocate channel d1 type disk;
backup
full
tag full_db
format '/u05/backup/rman/db_%t_%s_p%p'
(database);
release channel d1;
}

so i now have my backup safely on disk (and also tape)

i then deleted on of the datafiles from the users tablespace to simulate failure or user error with the database still open and then
ran the following.....

run {
allocate channel dev1 type disk;
sql "alter tablespace users offline immediate";
restore tablespace users;
recover tablespace users;
sql "alter tablespace users online";
release channel dev1;
}

this seemed to fix everything and the db was back up and running fully in no time....

Is it REALLY that simple? surely not - this seems to easy and makes me worried. Does this 'majically' apply redo etc from the backup
to bring it back up to current?

On another note is there any way to make RMAN delete archives it no longer requires? I'm surrently ending up with lots of full
bakups instead of say a weeks worth.

thanks

Tom

"Tom" <tomNOSPAM (AT) teameazyriders (DOT) com> schrieb im Newsbeitrag news:1066407262.69019.0 (AT) despina (DOT) uk.clara.net...


Lots of Greetings!
Volker

[...]
yes it is...

RMAN> configure retention policy to recovery window of 14 days;
as your default setting and then
RMAN> delete obsolete;
this deletes backups and copies older than 14 days
or directly
RMAN> delete obsolete recovery window of 14 days;

check the documentation though.

/G

On Fri, 17 Oct 2003 19:17:03 +0200, -={Giorgio}=-
<leva.md3496 (AT) mclink (DOT) it> wrote:

Exactly: it deletes *backups and copies*
To delete the original files you would need the
delete input
clause of the backup command


--
Sybrand Bakker, Senior Oracle DBA