RMAN Restoration Procedure

 The Process describes the DB cloning using RMAN backup of Source Database .


Step 1 : Crete a Pfile for Target database (mqtest)
If the Database is being dropped , retain the spfile of existing database .

Step 2 : Copy Password file from Source to target Server .

Password file will be in location $ORACLE_HOME/dbs
Password file name will be in format orapwORACLE_SID

copy the password file from Sorce server to target Server and rename the file to target DB name

Step 3 : Startup the database is Nomount State using Pfile (This step can be skipped if SPfile is already Availble )
SQL > start nomount pfile='$ORACLE_HOME/dbs/initmqtest.ora' ;
SQL > create spfile from pfile='$ORACLE_HOME/dbs/initmqtest.ora' ;
SQL > Shut immediaate ;

Step4: Startup DB again in Nomount stage and verify if DB is in Archivelog mode

set lines 550 pages 550
alter session set nls_date_format='DD_MM_YY HH24:MI' ;
col db_unique_name for a20
col instance_name for a20
Col startup_time for a25
select a.db_unique_name,b.INSTANCE_NAME,a.open_mode,b.STARTUP_TIME,to_char(SYSDATE,'DD-MM-YY HH24:MI'),
a.database_role,a.log_mode,a.flashback_on from gv$database a,gv$instance b WHERE A.inst_id=b.inst_id ;

show parameter db_create_file_dest  ;

select file_name from v$datafile ;



##### Datafiles should be In location for parameter db_create_file_dest#############
if Location are different

alter system set db_create_file_dest='*********' ;



step 5: Create a Rman Command file to Run Restoration process .

File_name - rman_restre_DATE.rman


connect auxiliary
 run
 {
    allocate auxiliary channel C1 type disk  ;
    allocate auxiliary channel C2 type disk  ;
    allocate auxiliary channel C3 type disk  ;
    DUPLICATE DATABASE TO mqtest BACKUP LOCATION '/archive/RMAN_BKP/' NOFILENAMECHECK  ;
    release auxiliary channel C1;
    release auxiliary channel C2;
    release auxiliary channel C3;
 }

Step 6 : Start the Rman Restoration .

nohup rman  cmdfile=rman_restre_DATE.rman log=rman_duplicate_script.log  &

Step 7 : Monitor the Process of Restoreation

tail -100f rman_duplicate_DATE.log

Step8 : Post Restoration Check Status of Database .

set lines 550 pages 550
alter session set nls_date_format='DD_MM_YY HH24:MI' ;
col db_unique_name for a20
col instance_name for a20
Col startup_time for a25
select a.db_unique_name,b.INSTANCE_NAME,a.open_mode,b.STARTUP_TIME,to_char(SYSDATE,'DD-MM-YY HH24:MI'),
a.database_role,a.log_mode,a.flashback_on from gv$database a,gv$instance b WHERE A.inst_id=b.inst_id ;

Step 9 : Convert DB into No archivelog mode if necessary .


 








Comments

Post a Comment

Popular posts from this blog

Cold Backup Cloning of Database .

 Cold Backup :  A cold backup is done when there is no user activity going on with the system. Also called as offline backup, is taken when the database is not running and no users are logged in. all files of the database are copied and no changes during the copy are made. Cold backup can be preformed when Database is in archive mode as well as Non archive log mode  . Backup Strategy :  Gather all the details of physical files (CRD) files in  database . redo log files are online redo log and archived redo log ones .   Select file_name,tablespace_name from dba_data_files  ; select * from v$controlfile  select member from v$logfile ; select name from v$archived_Log ;  create pfile from spfile  Backup  the contol file manually . alter database backup controlfile to trace as '/tmp/coldbackup_controlfile.sql' ;     Stop all the DB services (Database ,Listener)on source DB Server. Copy all the files(Datafiles,redologfiles,pfile,contol file backup) from source to backup location 
Read more

Find ALert log Location

 The alert log is an XML file that is a the log of messages and errors. Each alert log is specific to its component type, such as database, Oracle ASM, listener, and Oracle Clusterware. For the database, the alert log includes messages about the following:     Critical errors (incidents)     Administrative operations, such as starting up or shutting down the database,         recovering the database, creating or dropping a tablespace, and others.     Errors during automatic refresh of a materialized view     Other database events      Trace files are updated periodically over the life of the process and can contain information on the process environment,  status, activities, and errors. In addition, when a process detects a critical error,  it writes information about the error to its trace file.      Using Find Command    find $ORACLE_BASE -type f -name alert_$ORACLE_SID.log    select value from GV$DIAG_INFO WHERE name='Diag Trace';    find /opt/oracle -name alert*log
Read more

FRA Usage and Administration

Image
 In Oracle database, the Flash Recovery Area or FRA is a location on disk where the database can create and manage several kinds of backup and recovery-related files. Main file types are archivelog, flashback log, backups, as well as mirrors for your control files and redo log files. All files in the FRA are Oracle-managed files. Using a Flash Recovery Area simplifies the administration of your database by automatically retaining them for as long as they are needed for restore and recovery activities, and deleting them when they are no longer needed, because the space is needed for another backup and recovery-related purpose. Checking the current usage  You can check the configuration by looking at two parameters.The parameters are db_receovery_file_dest and second one db_recovery_file_dest_size .  db_receovery_file_dest point to location where the files will be located in Server . FOr normal single Databases this will be any directory for RAC this will be set to a Diskgroup whi
Read more