Question about RMAN

[arg_rommel]

Hello
I'm evaluating RMAN for one client.
I`ve tried a simple backup and recover using RMAN but I had a strange result. Maybe some of you can give me some answers.

First I did an:

rman target=usr/pwd@test nocatalog

RMAN> RUN {
1> allocate channel t1 type disk;
2> backup database format '/u01/app/oracle/admin/test/backup_%u';
3> release channel t1;

This generate a file in the directory above as I supposed.

Then I connect as user scott/tiger to the database test and truncated the table emp. The idea was that after recovering the database my emp table will be there as it was before the backup.

at last I did:

rman target=usr/pwd@test nocatalog

RMAN> RUN {
1> allocate channel t1 type disk;
2> restore database;
3> recover database;
4> release channel t1;

Every seems to be perfect but when I look for my emp table it was truncated as before the recover.
I don't understand the behaviour of the RMAN. Wasn't supposed to recover my emp table?

If someone can help me I'd be gratefull.
Thanks

[sambavan]

Is your db on the archive log mode? if so, rman will apply the archive logs to the DBA that had the information about the truncated table. On the other hand, if you recover with the option until scn, then you should see the dropped table.

Sam

[julian]

Originally posted by arg_rommel

If someone can help me I'd be gratefull.
Thanks

How can you expect the table *not* to be truncated as you recover without "set until time".

Check the time before you truncate, say it is 17.08.2003:14:30:00, and run:

run{
sql "alter session set nls_date_format = ''dd.mm.yyyy:hh24:mi:ss''";
set until time = '17.08.2003:14:30:00';
restore database;
recover database;
sql "alter database open resetlogs";
}

[arg_rommel]

Thank you for your answers. I 've been able to restore what I wanted using your advices.

Thanks!

Christian Villada