Re: Database Recovery

comments embedded.

abc_at_iom.com wrote:

> Ok, here's a scenario:
>
> There is a database--call it "MyDB" on server "A" Server A is Oracle
> 9i, Release 2 MyDb has never been backed up.
> However, all the files pertaining to that database (control, data,
> redo) have been copied to a safe place in another folder on that
> server.

If you ain't copied the datafiles either in hotbackup mode (begin backup / end backup, when myDB is up) or coldbackup (myDB is completely shut), these copied files are totally useless for restoration. I would also copy the archive logs, operational parameter file (init<sid>.ora) and operational password file (if any) to your safe place.

> Disaster strikes. The database server software installation is
> hopelessly screwed. No hope in hell of getting it reinstalled on that
> server.
>
> Fortunately, there's Server B! It has Oracle 9i Release 2 as well.
> In fact, it's the exact same installation as Server A--only this
> server works. The only instance running on Server B is some test db.
> I want Server B to "See" my original database, "MyDB". I copy the
> original physical files from the original database in question over to
> this new Server B.
>
> Now the question: How do I get Server B to recognize this new
> database? I'm sure it has something to do with RECOVER, RMAN, etc.
> But from reading the docs, all these commands assume that I have an
> instance up and running for this database I want to recover. I don't
> yet , of course, because Server B doesn't know that this MyDB even
> exists yet.

fortunately, if your able to access Server A in the event of a disaster, then copy all datafiles, redolog files, control files, archive logs, init<sid>.ora, password file to same dirs on Server B as they were in Server A, then set ORACLE_SID=myDB and startup the database. easy eh ?

> In short, how do I go from having raw Database files on a server to an
> actual running instance?
>
> For those of you who are familiar with SQL Server 2000, this is like
> the Attach/Detach command. In this case I would ATTACH this database
> and bring it on-line. But as you know, SQL Server and Oracle are two
> different animals.
>
> Any help appreciated.
>
Received on Sun Aug 18 2002 - 14:11:21 CDT