This document outlines procedures for restoring Oracle databases on two servers (pki-417.govca.net and pki-418.govca.net) running Linux Red Hat 5. The procedures involve disconnecting fiber optic ports, creating new disk groups using raw devices with ASM, clearing disk group contents, mounting the database in nomount state, restoring the control file and SPFILE from backups, and restoring and recovering data files using RMAN. The estimated completion time is 1-2 hours and involves the Oracle database team.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
This document outlines procedures for restoring Oracle databases on two servers (pki-417.govca.net and pki-418.govca.net) running Linux Red Hat 5. The procedures involve disconnecting fiber optic ports, creating new disk groups using raw devices with ASM, clearing disk group contents, mounting the database in nomount state, restoring the control file and SPFILE from backups, and restoring and recovering data files using RMAN. The estimated completion time is 1-2 hours and involves the Oracle database team.
This document outlines procedures for restoring Oracle databases on two servers (pki-417.govca.net and pki-418.govca.net) running Linux Red Hat 5. The procedures involve disconnecting fiber optic ports, creating new disk groups using raw devices with ASM, clearing disk group contents, mounting the database in nomount state, restoring the control file and SPFILE from backups, and restoring and recovering data files using RMAN. The estimated completion time is 1-2 hours and involves the Oracle database team.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
This document outlines procedures for restoring Oracle databases on two servers (pki-417.govca.net and pki-418.govca.net) running Linux Red Hat 5. The procedures involve disconnecting fiber optic ports, creating new disk groups using raw devices with ASM, clearing disk group contents, mounting the database in nomount state, restoring the control file and SPFILE from backups, and restoring and recovering data files using RMAN. The estimated completion time is 1-2 hours and involves the Oracle database team.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online from Scribd
Download as doc, pdf, or txt
You are on page 1/ 3
Oracle Database Restoratio Procedures
Prepared By Aml Kamal Ahmed
Reviewed By Ahmed Yasser
Version 1.0
Release Date 26 May 2009
Systems scope: Oracle Database: o Name: pki-417.govca.net o Name: pki-418.govca.net o IP: 10.67.20.217 o IP: 10.67.20.218 Operating systems scope: Linux redhat 5 Products scope: Restoration procedures having the following o Snapshot file. And knowing its location o The database ID Symptoms for procedure start: When database failed or damaged Teams involved: Oracle database team: Prepare the needed files used for backup Estimated completion time: From 1 hour to 2 hours Procedures:
System side: disconnecting the fiber optics ports to the oracle server . Oracle side: 1- Connect to any of the database nodes as the next procedures will be valid on both of the database nodes using putty software and xclock software to enable the GUI . 2- Standing on any of the nodes terminal windows. 3- Connecting to +asm instance using the syntax export oracle_sid = +ASM1 4- Run dbca command in the terminal to run the GUI of the creating and configuration of ASM and database. 5- Choose Create new diskgroup ASMDB from the screen appeared 6- Choose raw devices 6,7 from the next screen to the ASMDB diskgroup continue with default selection till finish. 7- Run dbca command again to create new disk group FlashDG. 8- Choose Create new diskgroup FlashDG from the screen appeared . 9- Choose raw devices 8,9 from the next screen to the FlashDG diskgroup continue with default selection till finish. 10-Verifying that the disk groups are mounted select name , state from v$asm_diskgroup ; How to check in new packages in to McAfee ePO 4.0 Procedures 2
11-Clear the content of the disk groups export oracle_sid= +ASM1 ASMCMD cd +ASM/Govprod rm -rf 12-Connect to sqlplus and put the database in nomount state sqlplus / as sysdba Startup nomount pfile = /home /oracle/new.ora; exit 13-Connect to rman backup and restore oracle tool using the next syntax a. Open terminal b. Type rman 14-After having the rman prompt appears type the following syntax a. Connect target / b. Set dbid=************* c. Restore control file from =ORACLE_HOME/dbs/snapcf_govprod1.f d. Create spfile from pfile= /home/oracle/new.ora; e. Shutdown immediate f. Sqlplus / as sysdba g. Startup mount
15-Restoring the data files. aRUN { ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE'; SEND 'NB_ORA_CLIENT=pki-0418vip,NB_ORA_POLICY=ORACLE_CLUSTER_BK,NB_ORA_SERV=pki0121,NB_ORA_SCHED=ORACLE'; Restore database; Recover database; RELEASE CHANNEL ch00; } balter database open reset logs
How to check in new packages in to McAfee ePO 4.0 Procedures
