<\/p>\n
If you can recover the redologs, you can do a complete recovery. Otherwise it is incomplete recovery. This also means there is data loss. Because all processes are not recovered.<\/p>\n
First, we will install Oracle RDBMS and Grid infrastructure. If the ASM intance is accessible, the disk group is ready and the Oracle binary is already installed, we can start installation.<\/p>\n
Let us assume that the database we will create is 2-node rac and the name ORCL. Suppose the DBID of our previous database is 1039438773. You can learn DBID information by connecting to rman.\u00a0 This information is also available in v$database view. Suppose we have already learned DBID information in some way. Even if you haven’t, you can find this information in old backup logs.<\/p>\n
The first process is to create the necessary directories in ASM disk groups.<\/p>\n
[oracle@db01 ~]$ . oraenv\r\nORACLE_SID = [ORCL1] ? +ASM1\r\nThe Oracle base remains unchanged with value \/u01\/app\/oracle\r\n[oracle@db01 ~]$ asmcmd\r\n\r\nASMCMD> cd DATA\r\nASMCMD> mkdir ORCL\r\nASMCMD> cd ORCL\r\nASMCMD> mkdir CONTROLFILE\r\nASMCMD> mkdir DATAFILE\r\nASMCMD> mkdir ONLINELOG\r\nASMCMD> cd ..\r\nASMCMD> ls\r\nDATA\/\r\nRECO\/\r\nASMCMD> cd RECO\r\nASMCMD> mkdir ORCL\r\nASMCMD> cd ORCL\r\nASMCMD> mkdir CONTROLFILE\r\nASMCMD> mkdir ONLINELOG\r\nASMCMD> mkdir ARCHIVELOG<\/pre>\n<\/p>\n
The directory specified by the audit_file_dest parameter in the file system must be created on all nodes.<\/p>\n
[root@db01 ~]# mkdir -p \/u01\/app\/oracle\/admin\/ORCL\/adump\r\n[root@db02 ~]# mkdir -p \/u01\/app\/oracle\/admin\/ORCL\/adump<\/pre>\n<\/p>\n
The next step is to create our pfile file or copy it from the backup to the corresponding directory ($ ORACLE_HOME \/ dbs). If you have Autobackup, you can also return your spfile file from autobackup.<\/p>\n
RMAN> RESTORE SPFILE FROM '\/backup_files\/c-1039438773-20160405-01';<\/pre>\n<\/p>\n
If you do not have a backup, you can create a pfile as below and register it with the name initORCL1.ora (init{SID}.ora).<\/p>\n
*.aq_tm_processes=2\r\n*.audit_file_dest='\/u01\/app\/oracle\/admin\/ORCL\/adump'\r\n*.audit_trail='db'\r\n*.cluster_database=true\r\n*.cluster_database_instances=2\r\n*.compatible='11.2.0.4.0'\r\n*.control_files='+DATA\/ORCL\/controlfile\/current.1842.908572993','+RECO\/ORCL\/controlfile\/current.21318.908572995'\r\n*.db_block_size=8192\r\n*.db_create_file_dest='+DATA'\r\n*.db_create_online_log_dest_1='+DATA'\r\n*.db_files=300\r\n*.db_name='ORCL'\r\n*.db_recovery_file_dest='+RECO'\r\n*.db_recovery_file_dest_size=3221225472000\r\n*.db_unique_name='ORCL'\r\n*.diagnostic_dest='\/u01\/app\/oracle'\r\n*.dispatchers='(PROTOCOL=TCP) (SERVICE=ORCLXDB)'\r\nORCL2.instance_number=2\r\nORCL1.instance_number=1\r\n*.job_queue_processes=1000\r\nORCL1.local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.225.16)(PORT=1521))))'\r\nORCL2.local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.225.14)(PORT=1521))))'\r\n*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'\r\n*.memory_max_target=20G\r\n*.memory_target=20G\r\n*.open_cursors=300\r\n*.processes=5000\r\n*.remote_listener='orcl-scan:1521'\r\n*.remote_login_passwordfile='exclusive'\r\n*.sessions=5505\r\n*.shared_servers=0\r\nORCL2.thread=2\r\nORCL1.thread=1\r\n*.undo_retention=1440\r\nORCL2.undo_tablespace='UNDOTBS2'\r\nORCL1.undo_tablespace='UNDOTBS1'<\/pre>\n<\/p>\n
If the disk group we want to restore the database is different from the disk group where the old database is located, the following lines must be in the pfile.<\/p>\n
*.log_file_name_convert='+OLD_DATA','+NEW_DATA','+OLD_RECO','+NEW_RECO'\r\n*.db_file_name_convert='+OLD_DATA','+NEW_DATA'<\/pre>\n<\/p>\n
We start the instance with pfile which we have created or restored.<\/p>\n
We set variables before. You can add variables to \/home\/oracle\/.bash_profile.<\/p>\n
Or you can add the following line to \/etc\/oratab and set it with oraenv.<\/p>\n
\/etc\/oratab content:<\/strong><\/p>\n
\u00a0ORCL1:\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1:N<\/pre>\n<\/p>\n
After adding this line, we can set all variables with oraaenv.<\/p>\n
[oracle@db01 ~]$ . oraenv\r\nORACLE_SID = [+ASM1] ? ORCL1\r\nThe Oracle base remains unchanged with value \/u01\/app\/oracle<\/pre>\n<\/p>\n
Now we can run sqlplus.<\/p>\n
[oracle@db01 ~]$ sqlplus \/ as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Fri Sep 30 15:20:57 2016\r\n\r\nCopyright (c) 1982, 2011, Oracle. All rights reserved.\r\n\r\nConnected to an idle instance.<\/pre>\n<\/p>\n
Let’s start Instance from the pfile file we created.<\/p>\n
SQL> startup nomount pfile='\/backup_files\/pfile_ORCL.ora';<\/pre>\n<\/p>\n
Then, we restore the control file with rman.<\/p>\n
RMAN> RESTORE CONTROLFILE from '\/backup_files\/c-1039438773-20160405-01';\r\n\r\nStarting restore at 08-APR-16\r\nusing target database control file instead of recovery catalog\r\nallocated channel: ORA_DISK_1\r\nchannel ORA_DISK_1: SID=4084 instance=ORCL1 device type=DISK\r\n\r\nchannel ORA_DISK_1: restoring control file\r\nchannel ORA_DISK_1: restore complete, elapsed time: 00:00:08\r\noutput file name=+DATA\/orcl\/controlfile\/current.1862.908626333\r\noutput file name=+RECO\/orcl\/controlfile\/current.22252.908626335\r\nFinished restore at 08-APR-16<\/pre>\n<\/p>\n
Let’s add the control file files to the pfile file that we created and restart the instance.<\/p>\n
The row of the control file in the new pfile:<\/p>\n
*.control_files='+DATA\/orcl\/controlfile\/current.1862.908626333','+RECO\/orcl\/controlfile\/current.22252.908626335'<\/pre>\n<\/p>\n
After the change, close the instance and reopen it as above.<\/p>\n
If the directory in which we copy the backups to restore is different from the paths in the control file, it is necessary to perform catalog operation from rman while in mount mode.<\/p>\n
Catalog operation with rman in mount mode:<\/strong><\/p>\n
SQL> startup mount pfile='\/backup_files\/pfile_ORCL.ora';<\/pre>\n<\/p>\n
With the command below, we make sure that the backups in the backup_files file are scanned and written to the control file.(this is catalog operation)<\/p>\n
RMAN> catalog start with '\/backup_files\/';<\/pre>\n<\/p>\n
While our database is in nomount mode, we start the restore and recover operations with the following script. With the “set until time” command, we are restoring to the point we specified. If you do not specify it, it will try to restore it until the last moment.<\/p>\n
Create a file named\u00a0restore_recover.sh with the following content and give the necessary permissions(755).<\/p>\n
We will run this file as follows.<\/p>\n
\/path_to_script\/restore_recover.sh<\/pre>\n<\/p>\n
If a different disk group is used, the names of the datafile must be changed and switch database operation is required before recover. The “set newname” command must be run for all datafiles. In this case, restore_recover.sh should be as follows.<\/p>\n
rman << EOF\r\nconnect target \/\r\nrun\r\n{\r\nset DBID=1039438773;\r\nsql 'alter database mount';\r\nset newname for datafile 1 to '+YENI_DATA';\r\nset newname for datafile 2 to '+YENI_DATA';\r\nset newname for datafile 3 to '+YENI_DATA';\r\nset newname for datafile 4 to '+YENI_DATA';\r\nset newname for datafile 5 to '+YENI_DATA';\r\nset newname for datafile 6 to '+YENI_DATA';\r\nset newname for datafile 7 to '+YENI_DATA';\r\nset newname for datafile 8 to '+YENI_DATA';\r\nset newname for datafile 9 to '+YENI_DATA';\r\nset newname for datafile 10 to '+YENI_DATA';\r\nset newname for datafile 11 to '+YENI_DATA';\r\nset newname for datafile 12 to '+YENI_DATA';\r\nrestore database;\r\nrestore archivelog all;\r\nswitch database to copy;\r\nset until time \"to_date('2016-04-06:00:00:00','yyyy-mm-dd:hh24:mi:ss')\";\r\nrecover database;\r\n}\r\nEOF<\/pre>\n<\/p>\n
If the disk group name is the same as before, the content of the restore_recover.sh file should be as follows.<\/p>\n
rman << EOF\r\nconnect target \/\r\nrun\r\n{\r\nset DBID=1039438773;\r\nsql 'alter database mount';\r\nrestore database;\r\nrestore archivelog all;\r\nset until time \"to_date('2016-04-06:00:00:00','yyyy-mm-dd:hh24:mi:ss')\";\r\nrecover database;\r\n}\r\nEOF<\/pre>\n<\/p>\n
When the processes are finished, the database and archive logs will be restored and recover will be done. After that, redo logs must also be processed.<\/p>\n
We are connecting with sql plus for processing redo logs.<\/p>\n
Because the redo logs that are used for all instances in RAC databases are connected, it will request the redologs that are needed to perform complete recovery when you run the following command.<\/p>\n
SQL> recover database using backup controlfile until cancel;<\/pre>\nAfter the line specified by “Specify log:”, you must specify the corresponding redo log. The “Log applied” result is returned when all the required redo logs are recovered.<\/p>\n
You can find the entire script below.<\/p>\n
[oracle@db01 ]$ sqlplus \/ as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Fri Apr 8 14:07:29 2016\r\n\r\nCopyright (c) 1982, 2011, Oracle. All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n\r\n\r\nSQL> recover database using backup controlfile until cancel;\r\nORA-00279: change 562385338311 generated at 04\/05\/2016 17:44:09 needed for\r\nthread 1\r\nORA-00289: suggestion : +RECO\r\nORA-00280: change 562385338311 for thread 1 is in sequence #1607\r\n\r\n\r\nSpecify log: {<RET>=suggested | filename | AUTO | CANCEL}\r\n\/backup_files\/ONLINELOG\/group_12.11832.858521665\r\nORA-00279: change 562385338311 generated at needed for thread 2\r\n\r\n\r\nSpecify log: {<RET>=suggested | filename | AUTO | CANCEL}\r\n\/backup_files\/ONLINELOG\/group_22.2629.858521677\r\nLog applied.\r\nMedia recovery complete.<\/pre>\n<\/p>\n
So we have completed a complete recovery. In this case, we can open our database directly.<\/p>\n
RMAN> alter database open;<\/pre>\n<\/p>\n
Otherwise we need to open it by specifying resetlogs.<\/p>\n
RMAN> alter database open resetlogs;\r\n\r\ndatabase opened<\/pre>\n<\/p>\n
Since our database has been opened, we can begin operations after restore.<\/p>\n
First, create the spfile from the pfile:<\/strong><\/p>\n
SQL> create spfile='+DATA\/ORCL\/spfileORCL.ora' from pfile='\/backup_files\/pfile_ORCL.ora';<\/pre>\n<\/p>\n
Change the contents of the pfile (initORCL1.ora) under the $ORACLE_HOME\/dbs directory as follows:<\/strong><\/p>\n
SPFILE='+DATA\/ORCL\/spfileORCL.ora'<\/pre>\n<\/p>\n
Set a password for the SYS user:<\/strong><\/p>\n
SQL> alter user sys identified by your_sys_password;<\/pre>\n<\/p>\n
Create Orapw file:<\/strong><\/p>\n
[oracle@db01 ~]$ cd $ORACLE_HOME\/dbs\r\n[oracle@db01 ~]$ orapwd file=orapwORCL1 password=Welcome1 entries=5<\/pre>\n<\/p>\n
If necessary, add new members to the redo log groups:<\/strong><\/p>\n
SQL> ALTER DATABASE ADD LOGFILE MEMBER '+RECO' TO GROUP 1;\r\nSQL> ALTER DATABASE ADD LOGFILE MEMBER '+RECO' TO GROUP 2;\r\nSQL> ALTER DATABASE ADD LOGFILE MEMBER '+RECO' TO GROUP 3;<\/pre>\n<\/p>\n
If you have not set the local_listener and remote_listener parameters, set it:<\/strong><\/p>\n
We created this information for all nodes when creating pfile.<\/p>\n
SQL> show parameter listener\r\n\r\nNAME TYPE VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlistener_networks string\r\nlocal_listener string (DESCRIPTION=(ADDRESS_LIST=(AD\r\nDRESS=(PROTOCOL=TCP)(HOST=172.\r\n16.225.16)(PORT=1521))))\r\nremote_listener string orcl-scan:1521<\/pre>\n<\/p>\n
Let’s add the new database and instances to CRS:<\/strong><\/p>\n
[oracle@db01 ]$ srvctl add database -d ORCL -o \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1 -p '+DATA\/ORCL\/spfileORCL.ora' -n ORCL\r\n[oracle@db01 ]$ srvctl add instance -d ORCL -i ORCL1 -n db01\r\n[oracle@db01 ]$ srvctl add instance -d ORCL -i ORCL2 -n db02<\/pre>\n<\/p>\n
After copying the necessary files to the second node and creating a second undo tablespace, we can start instance on that node.<\/p>\n
Files to copy:<\/strong><\/p>\n
db01:$ORACLE_HOME\/dbs\/initORCL1.ora --> db02:$ORACLE_HOME\/dbs\/initORCL2.ora\r\ndb01:$ORACLE_HOME\/dbs\/orapwORCL1 --> db02:$ORACLE_HOME\/dbs\/orapwORCL2<\/pre>\n<\/p>\n
The creation of the undo tablespace for the second node:<\/strong><\/p>\n
CREATE UNDO TABLESPACE UNDOTBS2 DATAFILE \r\n'+DATA' SIZE 10G AUTOEXTEND ON NEXT 5M MAXSIZE UNLIMITED\r\nONLINE\r\nRETENTION NOGUARANTEE\r\nBLOCKSIZE 8K\r\nFLASHBACK ON;<\/pre>\n<\/p>\n
Creating a redo log group for the second node and adding a new member:<\/strong><\/p>\n
The size should be the same as that created for the other instance. Group numbers must be different from those created for the other instance.<\/p>\n
SQL> ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 4 '+DATA' SIZE 500m;\r\n\r\nDatabase altered.\r\n\r\nSQL> ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 5 '+DATA' SIZE 500m;\r\n\r\nDatabase altered.\r\n\r\nSQL> ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 6 '+DATA' SIZE 500m;\r\n\r\nDatabase altered.\r\n\r\nSQL> ALTER DATABASE ADD LOGFILE MEMBER '+RECO' TO GROUP 4;\r\n\r\nDatabase altered.\r\n\r\nSQL> ALTER DATABASE ADD LOGFILE MEMBER '+RECO' TO GROUP 5;\r\n\r\nDatabase altered.\r\n\r\nSQL> ALTER DATABASE ADD LOGFILE MEMBER '+RECO' TO GROUP 6;\r\n\r\nDatabase altered.<\/pre>\n<\/p>\n
At this stage, we can close the database and open it with srvctl in all instances.<\/p>\n
SQL> shu immediate<\/pre>\n[oracle@db01 ]$ srvctl start database -d ORCL\r\n[oracle@db01 ]$ srvctl status database -d ORCL\r\nInstance ORCL1 is running on node db01\r\nInstance ORCL2 is running on node db01<\/pre>\nNow, our RAC database is open and runs on 2 nodes.<\/p>\n\n
<\/div>\n