Hi, Please see the procedure below found in symantec site. That will surely help you.
Link:
http://seer.entsupport.symantec.com/docs/240306.htm
How to perform a disaster recovery of an Oracle server using the Backup Exec Agent for Oracle Server
--------------------------------------------------------------------------------
Details:
The following are the pre-requisites to fully recover an Oracle database server in the event a disaster occurs:
1. A FULL Oracle database server file system backup using Backup Exec (tm): When making this backup, make sure the Oracle database is shut down and include all the Oracle database directories as well as the Windows NT/2000 system directory. This backup set will contain a FULL CLOSED Oracle Database backup. A FULL Oracle database backup should be performed every time any changes are made to the physical and/or logical structure of the Oracle database and forms the base for recovering the database server to a fully working order.
2. Using the Agent for Oracle Server, an up to date, FULL ONLINE backup containing the Oracle database tablespace datafiles, the Archive log files and the Control file
With these backups, the Oracle database server can be recovered up to the time of the latest FULL ONLINE backup in case a disaster occurs.
Recovering an Oracle Database Server from a disaster.
If an Oracle database server experienced a disaster such as a hard disk failure, use this procedure to recover the server and the Oracle databases:
1. Recover Windows NT/2000 on the Oracle database server using the appropriate disaster recovery procedure listed in the Related Documents section of this TechNote.
NOTE: When the related instructions say to restore the last full backup, be sure to use the last full backup containing the FULL CLOSED backup of the Oracle database server
NOTE: Because the full system backup was restored, the computer is booted using its original version of Windows NT/2000. The system now contains the original version of Windows NT/2000, the Backup Exec Agent for Oracle Server, the Oracle databases including the tablespace datafiles, all Oracle system files, and any other files contained on the full backup media.
2. At the Oracle database server, start Server Manager
(NOTE: In Oracle 9i use SQLPlus and connect as sysdba. See the Related Documents section below for this procedure), connect to the database as Internal and at the prompt, type:
SHUTDOWN IMMEDIATE
Then press <Enter>
3. At the media server, run another restore operation. This time, using the Agent for Oracle Server, restore the storage media containing the latest FULL ONLINE backup containing all the Oracle database tablespace datafiles, the archive log files and the control file. In the Restore Job Properties Advanced tab (For versions 9.x and above, this will be in the General tab) , make sure that Restore over Existing files is selected.
NOTE: It is vital that all archive logs, archived between the time of the FULL CLOSED Oracle database backup and the latest FULL OPEN database backup, are made available for the database recovery. Check this, and if necessary, refer to the alert log (<SID>ALRT.LOG) for the archive log sequence numbers required, as well as the location where Oracle will expect them to be available.
4. When the restore operation completes, move to the Oracle database server
5. Start server manager, connect as Internal and start the database but only mount it by typing:
STARTUP MOUNT
Then press <Enter>
6. When the database is mounted, type:
RECOVER DATABASE USING BACKUP CONTROLFILE
Then press <Enter>
Oracle will respond to this command by returning the following message, suggesting a log sequence to apply.
ORA-00279: Change 36579 generated at <time/date> needed for thread 1
ORA-00289: Suggestion : \Oracle_Home\Oradata\<SID>\%SID%T00036579.ARC
ORA-00280: {<RET>=Suggested | filename | AUTO | FROM logsource | CANCEL}
7. At the prompt, type:
AUTO
Then press <Enter>
This will automatically apply all archived log sequences required to recover the database (assuming all archived redo logs are available in the location specified in the init.ora parameter and that the format corresponds to the format specified).
It is possible that a final non-archived log sequence is requested to complete the recovery. This will only hold one System Change Number (SCN) and no transactions relating to the database, up to, and including the time of the FULL ONLINE Oracle backup. If this is the case, the following message will be returned by Oracle:
ORA-00308: cannot open archived log
'E:\ORACLE\ORADATA\KIMSTAD\ARCHIVE\KIMSTADT00036949.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
8. To finish the recovery, stay in server manager with the database mounted, and type:
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE
Then press <Enter>
9. When Oracle requests this final sequence again, type:
CANCEL
Then press <Enter>
10. Oracle will return the following message:
Media recovery canceled
The media recovery of the database is complete.
11. To open the database and to synchronize the log sequence, type:
ALTER DATABASE OPEN RESETLOGS
Then press <Enter>
The Oracle database server is now restored to full working order up to the time of the latest full online Oracle backup.
Kindly mark as solution!
Thanks
