step by step recovery from hot backup

[bookouri]

OK, Ive got my hot backups, does anybody have a step by step guide/howto that they use/recommend to take those hot backups to a new machine that has 9i installed and bring that database back on line and recover it?

thanks for any suggestions

 

[SantaMufasa]

Bookouri,

Here are the steps (off the top of my head versus actually trying/testing them out on my machine):

First, since you didn't mention the o/s, let's presume a *nix operating system in this example.

For the sake of brevity, let's refer to the source machine as M1 and the target machine as M2 (not to be confused with major motorways in the UK). The source database on M1 will be D1 and the target database on M2 is D2.

Since you said:

...take those hot backups to a new machine that has 9i installed and bring that database back on line and recover it...

...this makes me presume that D1 is already down. If D1 is running, then there will be a point, below, where you may need to shut it down briefly.

Steps:

1) Ensure that M2 has the same file-system references that M1's D1 uses. For example, if the datafile for the SYSTEM tablespace in D1 is "/u01/oracle/data1/SYSTEM01.dbf", then ensure that "u01/oracle/data1" directory structure exists on M2.

2) The D2 instance does not need to be the same name as the D1 instance. Ensure that an entry exists in the "/var/opt/oracle/oratab" file (on Solaris)..."/etc/oratab" (on all other *nix o/s) that defines the instance name, $ORACLE_HOME, and startup flag for the D2 instance.

3) Copy the D1 initD1.ora (and D1 spfile) over to their counterpart locations on M2.

4) Copy D1's hot backup files to M2 into the exact-same-named locations there as D1's database datafiles on M1.

5) Copy the ARCHIVED REDO LOG FILES that have been created since the hot backup, from M1 to the same locations on M2.

6) (If D1 is not shutdown, shut it down now.) Copy D1's CONTROL FILES and ON-LINE REDO LOG FILES from M1 into the same locations on M2.

7) On M2, as an Oracle administrator o/s login, issue the o/s command, ". oraenv" to properly set your $ORACLE_SID and $ORACLE_HOME variables.

8) "sqlplus /nolog"..."SQL> connect / as sysdba"

9) "SQL> startup mount"

10) "SQL> recover database"

11) ...following successful recovery, "SQL> ALTER DATABASE OPEN;"...you should be good to go.

Let me know if my aging mind steered you right or wrong.

Mufasa
(aka Dave of Sandy, Utah, USA)
[

http://www.dasages.com:

Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.

 

[bookouri]

thanks, Im going to give it a try...Ill let you know how it turns out...

 

[SantaMufasa]

Bookouri, An additional item...if your parameter (init...or spfile) file makes specific reference to "SID=..." or "SERVICE_NAME=...", then you will need to ensure that the D2 SID matches those entries.

Mufasa
(aka Dave of Sandy, Utah, USA)
[

http://www.dasages.com:

Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.