Recovering the complete Oracle instance or
database to a computer other than the original Oracle server
If you experience a
complete loss, deletion, or destruction of the Oracle instance or
database, you can restore the instance and database to a computer
other than the original Oracle server.
To successfully complete
the recovery, you must have the following items:
Table: Requirements when you recover using a new
or alternate Oracle server
Item
|
Description
|
DBID
|
If you do not know the DBID, you can find it in the Backup Exec
job log or in RMAN after you login.
|
ControlFile piece ID
|
You can identify the ControlFile piece ID in the Backup Exec
restore view in the Control Files subnode under the Oracle
node.
|
A full system Oracle backup
|
The full system Oracle backup must include the
following:
-
controlfile
-
datafiles
-
archive logs
|
To recover the complete Oracle instance and
database after it has been lost, deleted, or destroyed, and you
want to use a new or alternate Oracle server for the recovery
-
Recreate the Oracle
instance using the same name you used for the original instance
that was lost.
-
Find and rename the
pwd<SID>.ora file.
-
Create a new
pwd<SID>.ora file.
To create a new pwd<SID>.ora file
-
Open a command
prompt.
-
Type the following
command:
orapwd
file=path\pwdsid.ora password=<password>
To continue the disaster recovery
-
In the command prompt, do
the following:
-
Type the following
command:
RMAN
-
Type CONNECT TARGET
<sys/password@sid>;
-
Type SHUTDOWN ABORT;
-
Type STARTUP NOMOUNT;
-
Type SET DBID<dbid ID>;
-
Move to the Backup Exec
media server.
-
On the navigation bar,
click the arrow next to Restore.
-
Click .
-
On the Properties pane,
under Source, click .
-
Select the appropriate
ControlFile to restore.
-
On the Restore job
properties pane, under Destination, click .
-
Check the check box for
the option, .
-
Enter account credentials
to access the new or alternate Oracle server.
-
Check the check box for
the option,
-
Type a path to the new
database.
-
Check the check box for
the option,
-
Click .
The restore job will fail
because the recovery portion encounters inconsistent archive logs.
This is a normal occurrence during a disaster recovery.
-
Move to the Oracle
server.
-
Type Alter database open resetlogs;
-
Do one of the
following:
If an error is encountered while Oracle tries to open the
database
|
Note the online redo log path and then update the path using the
steps below.
|
If an error does not occur
|
Do nothing. The disaster recovery is complete.
|
To update the online redo log file path
-
At the Oracle server,
open a command prompt.
-
Type the following
command:
SQLPLUS
/nolog
-
Type connect<sys/password@SID>;
-
Type the following
SQLPlus command:
SQLPLUS
ALTER DATABASE RENAME FILE <old path from backup to any redolog
file name> to <path to expected restored redolog file
name>;
For example,
ALTER DATABASE RENAME
FILE 'D:\ORACLE\ORADATA\JACOB\REDO01.LOG' to
'C:\ORACLE\ORADATA\JACOB\REDO01.LOG';
-
In the command prompt,
type RMAN.
-
Type the following
command at the RMAN prompt:
Alter
database open resetlogs;
-
Close the command
prompt.
The recovery is
finished.