1. Copy the backup pieces to another server !!!! If the filesystem paths
are different , use soft-links to setup the directory paths for the backup
pieces and the target locations for controlfile, redo, datafiles
2. Hopefully a controlfile backup was made as the last backup -- in that
case it would be the "newest" backup piece. (Else, use "strings -a" on the
files)
3. Create a pfile
4. RMAN RESTORE CONTROLFILE FROM ..
5 . RMAN LIST BACKUP and verify that it shows all the datafiles (or LIST
BACKUP COMPLETED SINCE "to_date(day_before_the_drop_table)"
6. Then you don't need to run CATALOG
7. ALTER DATABASE MOUNT
8. RECOVER DATABASE UNTIL ...
9. OPEN RESETLOGS
Hemant K Chitale
On Wed, Mar 22, 2023 at 1:22 AM Sandra Becker <sbecker6925@xxxxxxxxx> wrote:
OS: Solaris 5.8
Oracle: 9.2.0.8 ( I knew this would bite us one day, but I have no
control over it.)
Problem: Someone purged all the data from a single table, now they want
it recovered to a P-I-T
Backups are still on disk, but have aged out. When I list backup of
datafile 1, it shows the oldest backup is one day after the one I need.
Unfortunately, you can't catalog backups in 9i. We also no longer have
Oracle support because the company thought it was a waste of money. Is
there anything I can do to duplicate a new database from the backups I need?
Also unfortunate that the production database and the clone are on the
same server. Again, I had no choice in the matter. Am I totally screwed
in recovering that table?
--
Sandy B.
