Cold Backup/Recovering A Table

Question

I am running 11r2 in a RAC environment. We have a primary plus two standby's (using Active Data Guard). Also, I am a new DBA, so bare with me. :)
TableX in a certain database is corrupted. The corruption began a month ago due to a web developer's code change. The code change was fixed a week ago.
Summary: the data in TableX is corrupted up until a week ago.
Flashback doesn't extend that far into the past, so what I've been thinking of doing is, on our test server:
1) Copy over relevant files from production to the test server
2) Backup the original TableX on production
3) Restore the system, sysaux, undo and the tablespace which contains TableX on test server
4) Drop all other tablespaces in mount state (or not, if this step isn't necessary?)
5) Recover the database till the time when the table was dropped or updated
6) Take an export of TableX from database and import it into production, overwriting the current TableX
7) Update the imported production TableX with the past week of "good" data from the backup in step 2
I have 3 questions.
Does this seem like a good strategy?
Additionally, I am having difficulty determining what the "relevant files" are in step 1. What would I be copying over? Everything in the ArchiveLog folder? Or Everything in the db_recovery_file_dest folder? Or...?
Lastly, in step 3, is there a way to perform the restore w/o overwriting preexisting data on the test server?
Thank you

Answer 1

Hemant K Chitale wrote:
is there a way to perform the restore w/o overwriting preexisting data on the test serverYou would have to restore to a different folder and when you ALTER DATABASE MOUNT you ALTER DATABASE RENAME DATAFILE to specify the new locations of the datafiles.
I think the MOUNT is the step that I was missing, though it seems so obvious now...
1) Copy over relevant files from production to the test server
2) Backup the original TableX on production
*2.5) MOUNT the copied data files onto the test server*
3) Restore the system, sysaux, undo and the tablespace which contains TableX on test server
4) Drop all other tablespaces in mount state (or not, if this step isn't necessary?)
5) Recover the database till the time when the table was dropped or updated
6) Take an export of TableX from database and import it into production, overwriting the current TableX
7) Update the imported production TableX with the past week of "good" data from the backup in step 2
Last Question (I think): you both refer to "THE cold backup." We use a diff backup. I assume you mean "copy over all files since the last full backup prior to the date that data corruption began"?