Recovering the complete Oracle instance and database using the original Oracle server

If you experience a complete loss, deletion, or destruction of the Oracle instance or database, you can use the same Oracle server for the recovery. You can also use these instructions when you configure a new physical server that uses the same server name and SID name.

To successfully complete the recovery using this scenario, you must have the following items:

Table: Requirements when you recover using the original 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

The original Oracle server

To successfully recover the Oracle system using disaster recovery scenario 1, you must restore to the original Oracle server.

To recover the complete Oracle instance or database after it has been lost, deleted, or destroyed, and you want to use the original Oracle server for the recovery

  1. Recreate the Oracle database using the same name you used for the original database that was lost.

  2. Find and rename the pwd<SID>.ora file.

  3. Create a new pwd<SID>.ora file.

To create a new pwd<SID>.ora file

  1. Open a command prompt.

  2. Type the following command:

    orapwd file=path\pwdsid.ora password=<password>

To continue the disaster recovery

  1. Open a command prompt and do the following:

  2. Type the following command:

    RMAN

  3. Type CONNECT TARGET <sys/password@sid>;

  4. Type SHUTDOWN ABORT;

  5. Type STARTUP NOMOUNT;

  6. Type SET DBID<dbid ID>;

  7. Move to the Backup Exec media server.

  8. On the navigation bar, click the arrow next to Restore.

  9. Click New Restore Job.

  10. On the Properties pane, under Source, click Selections.

  11. Select the appropriate ControlFile for restore.

  12. Click Run Now.

    The restore job will fail because the recovery portion encounters inconsistent archive logs. This is a normal occurrence during a disaster recovery.

  13. After the restore job finishes, exit Backup Exec.

  14. Move to the Oracle server.

  15. In the command prompt, type the following command at the RMAN prompt:

    Alter database open resetlogs;

  16. Close the command prompt.

    The recovery is finished.