Skip to main content

Step by Step How to Create Physical Standby Database using RMAN Backup Restore


How to Setup Physical Standby Database using RMAN Backup Restore- Quick and Dirty way

Assumption:
It is assumed that you already have single instance database installed and configured and you want to setup physical standby database for this primary database to protect you data from disaster recovery etc.
Installation and configuration of a single instance database using ASM is explained in following posts

Here is the details of my Primary database for which I want to configure the Physical standby database.
Hosts and Databases Used in this Example
DB_ROLE PRIMARY STANDBY
HOST_NAME test1 test2
DB_UNIQUE_NAME TST1TP TST1TS
DB_NAME TST1T TST1T
That's said lets start .....
Step1> Prepare your primary database to support physical standby database
  • Put the database in Archivelog mode
If the primary database is not already in archivelog mode, put it in archive log mode
SQL> alter system set log_archive_dest_1='location=/u01/dbatst1/stage/archive/';
System altered.
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size                  8794848 bytes
Variable Size            1912605984 bytes
Database Buffers          218103808 bytes
Redo Buffers                7979008 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     4146
Next log sequence to archive   4148
Current log sequence           4148
Check out How to Enable Archive Log Mode in Oracle Database for more details
  • Disabling Active Data Guard
NOTE: This step is optional and only needed if you don't want to use Oracle Active Dataguard Option or You don't have Licence for it. Since this is an static parameter it requires downtime.
SQL> alter system set "_query_on_physical"=FALSE scope=spfile;

System altered.

SQL> startup force;

ORACLE instance started.

Total System Global Area 2147483648 bytes

Fixed Size                  8794848 bytes

Variable Size            1912605984 bytes

Database Buffers          218103808 bytes

Redo Buffers                7979008 bytes

Database mounted.

Database opened.

SQL> show parameter "_query_on_physical"

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

_query_on_physical                   boolean     FALSE
  • Activating Standby File Management
SQL> alter system set standby_file_management=AUTO scope=both;

System altered.

SQL> show parameter standby_file_management

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

standby_file_management              string      AUTO

  • Enable forced logging
SQL> alter database force logging;

Database altered.

SQL> select force_logging from v$database;

FORCE_LOGGING

---------------------------------------

YES

Read more about force logging Check out Oracle Database Logging Mode and Enhancements in 18c

  • Setting Unique name
DB_UNIQUE_NAME parameter of primary and standby database must be unique. As mentioned in the beginning itself I am using TST1TP as DB_UNIQUE_NAME  for Primary database
SQL> alter system set db_unique_name='TST1TP' scope=spfile;

System altered.

SQL> startup force;

ORACLE instance started.

Total System Global Area 2147483648 bytes

Fixed Size                  8794848 bytes

Variable Size            1912605984 bytes

Database Buffers          218103808 bytes

Redo Buffers                7979008 bytes

Database mounted.

Database opened.

SQL> show parameter unique

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

db_unique_name                       string      TST1TP
Step2> On Standby Database Server (test2) Install oracle database Binaries - same Oracle version as Primary Database
For Step by step instruction navigate to Oracle 12c Database Software Only Installation in Silent Mode
Step3> Optionally if using ASM
Install and configure ASM and ASM Diskgroups. Steps are provided at Installing and Configuring Oracle Grid Infrastructure for Standalone Server in Silent Mode
Step4> Configure Oracle Network Files
  • Configuring TNSNAMES.ORA file
Configuring tnsnames.ora file
Prepare the tns entry for both primary as well as stanby and enter in $ORACLE_HOME/network/admin/tnsnames.ora file in both primary and physical stanby database servers
TST1TP =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP) (HOST = test1.oracle.com)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = TST1TP)
      (UR = A)
    )
  )
TST1TS =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP) (HOST = test2.oracle.com) (PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = TST1TS)
      (UR = A)
    )
  )
Step5> Create pfile from Primary for standby
SQL> create pfile='/u01/dbatst1/stage/initTST1TS.ora' from spfile;
File created.
Step6> Transfer the PFILE on Standby Server at $ORACLE_HOME/dbs
$ scp /u01/dbatst1/stage/initTST1TS.ora oracle@test2:/u01/app/oracle/12.2.0.1/dbp1/dbs/

Step7> Create standby controlfile
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/u01/dbatst1/stage/backup/stby.ctl';
Database altered.
Step8> Transfer Standby Controlfile on Standby Server
$scp  /u01/dbatst1/stage/backup/stby.ctl oracle@test2:/u01/app/oracle/12.2.0.1/dbp1/dbs/
Step9> modify the Pfile on Standby Server as shown below
*.db_unique_name='TST1TS'
*.control_files='/u01/app/oracle/12.2.0.1/dbp1/dbs/stby.ctl'
Optionally
NOTE:-If you have different file system/ASM DISK GROUP structure between Primary and standby then modify the following parameter accordingly
db_create_file_dest='ASM_DISKGROUP OR FILESYSTEM'
db_create_online_log_dest_1='ASM_DISKGROUP OR FILESYSTEM'
db_create_online_log_dest_2='ASM_DISKGROUP OR FILESYSTEM'
Step10> Create Required directories on Standby Server
$ mkdir -p /u01/app/admin/TST1T/adump
Step11>  On Standby Server Set Environment variables and start the instance
$ export ORACLE_HOME=/u01/app/oracle/12.2.0.1/dbp1
$ export ORACLE_SID=TST1T
$ export PATH=$ORACLE_HOME/bin:$PATH
$ sqlplus "/as sysdba"
SQL*Plus: Release 12.2.0.1.0 Production on Thu Jan 24 13:27:03 2019
Copyright (c) 1982, 2016, Oracle.  All rights reserved.
Connected to an idle instance.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size                  8794848 bytes
Variable Size            1912605984 bytes
Database Buffers          218103808 bytes
Redo Buffers                7979008 bytes
Step12> create spfile from pfile
SQL> create spfile from pfile;
File created.
Step13> Restart the Standby  database in mount mode
SQL> shut immediate;
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size                  8794848 bytes
Variable Size            1912605984 bytes
Database Buffers          218103808 bytes
Redo Buffers                7979008 bytes
Database mounted.
Step14> Perform full Primary database backup inluding archivelogs
$rman target /
RMAN>run
{
  ALLOCATE CHANNEL ch1 TYPE DISK MAXPIECESIZE 10G;
  BACKUP
  FORMAT '/u01/dbatst1/stage/backup/back_%U'
  DATABASE
  PLUS ARCHIVELOG
  FORMAT '/u01/dbatst1/stage/backup/back_%U';
  RELEASE CHANNEL ch1;
}

Step15> Transfer backup pieces on Standby Server
$ scp -r /u01/dbatst1/stage/backup oracle@test2:/u01/app/stage
Step16> Catalog the backup pieces : On Standby Server
$ rman target /
RMAN> catalog start with '/u01/app/stage/backup/';
using target database control file instead of recovery catalog
searching for all files that match the pattern /u01/app/stage/backup/
List of Files Unknown to the Database
=====================================
File Name: /u01/app/stage/backup/back_a5to514c_1_1
File Name: /u01/app/stage/backup/back_a6to514k_1_1
File Name: /u01/app/stage/backup/back_a8to515c_1_1
File Name: /u01/app/stage/backup/back_a7to5153_1_1
File Name: /u01/app/stage/backup/back_a4to514a_1_1
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /u01/app/stage/backup/back_a5to514c_1_1
File Name: /u01/app/stage/backup/back_a6to514k_1_1
File Name: /u01/app/stage/backup/back_a8to515c_1_1
File Name: /u01/app/stage/backup/back_a7to5153_1_1
File Name: /u01/app/stage/backup/back_a4to514a_1_1
Step17>On Standby Restore database using restore database.
$ rman target /
RMAN> run
{
  ALLOCATE CHANNEL ch1 TYPE DISK;
  RESTORE DATABASE;
  RELEASE CHANNEL ch1;
}
using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=785 device type=DISK
Starting restore at 29-JAN-19
channel ch1: restoring datafile 00001
input datafile copy RECID=23 STAMP=998822543 file name=+DG_TEST_DATA/TST1TS/DATAFILE/system.273.998821513
destination for restore of datafile 00001: +DG_TST_DATA/TST1T/DATAFILE/system.274.990371801
channel ch1: copied datafile copy of datafile 00001
.................................................................
.................................................................
Finished restore at 29-JAN-19
released channel: ch1
Step 18: Transfer Primary database password file to standby database
$ scp $ORACLE_HOME/dbs/orapwTST1T oracle@test2:$ORACLE_HOME/dbs/
Rename the password file to the standby database name.
NOTE: The password file name must match the instance name/SID used at the standby site, not the DB_NAME.

Step 19: Restart the Standby Database
$ sqlplus "/as sysdba"
SQL> startup mount force;
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size                  8794848 bytes
Variable Size            1912605984 bytes
Database Buffers          218103808 bytes
Redo Buffers                7979008 bytes
Database mounted.
Step 20: Configure Logshipping
On Primary Database
SQL> alter system set log_archive_dest_2='service=TST1TS';
System altered.

SQL> alter system set log_archive_dest_state_2=enable;
System altered.
SQL> alter system switch logfile;
System altered.
NOTE1:On Standby database server  verify and ensure (using lsnrctl services command) that the Listener is listening for service 'TST1TS' 
NOTE2:On Primary database server  verify and ensure (using tnsping TST1TS ) that the TNSENTRY for 'TST1TS' exists

 Step 21: On Standby Start Apply Process
SQL> recover managed standby database disconnect from session;
Media recovery complete.
Step 22: Verify the Configuration of Standby database.

SQL> select name,DB_UNIQUE_NAME,open_mode,database_role from v$database;

NAME      DB_UNIQUE_NAME                 OPEN_MODE            DATABASE_ROLE
--------- ------------------------------ -------------------- ----------------
TST1T     TST1TS                         MOUNTED              PHYSICAL STANDBY

SQL> select PROCESS,STATUS,THREAD#,SEQUENCE# from v$managed_standby;

PROCESS   STATUS          THREAD#  SEQUENCE#
--------- ------------ ---------- ----------
ARCH      CONNECTED             0          0
DGRD      ALLOCATED             0          0
DGRD      ALLOCATED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
RFS       IDLE                  1       4522
RFS       IDLE                  0          0
RFS       IDLE                  0          0
RFS       IDLE                  0          0
RFS       IDLE                  0          0

PROCESS   STATUS          THREAD#  SEQUENCE#
--------- ------------ ---------- ----------
MRP0      WAIT_FOR_LOG          1       4522

12 rows selected.

Switch a logfile on Primary and Verify the Status again
SQL> alter system switch logfile;
System altered.
SQL> /

PROCESS   STATUS          THREAD#  SEQUENCE#
--------- ------------ ---------- ----------
ARCH      CONNECTED             0          0
DGRD      ALLOCATED             0          0
DGRD      ALLOCATED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
RFS       IDLE                  1       4523
RFS       IDLE                  0          0
RFS       IDLE                  0          0
RFS       IDLE                  0          0
RFS       IDLE                  0          0

PROCESS   STATUS          THREAD#  SEQUENCE#
--------- ------------ ---------- ----------
MRP0      WAIT_FOR_LOG          1       4523
12 rows selected.

Comments

Post a Comment

Popular posts from this blog

DataPump Import Of Object Types Fails With Errors ORA-39083 ORA-2304 Or ORA-39117 ORA-39779

<<Back to Oracle DATAPUMP Main Page ORA-39083: Object type TYPE:"TEST_QA01"."LOG_RECORD" failed to create with error: ORA-02304: invalid object identifier literal Import: Release 12.1.0.2.0 - Production on Tue May 29 07:59:12 2018 Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security, OLAP, Advanced Analytics and Real Application Testing options Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded Starting "SYSTEM"."SYS_IMPORT_FULL_01":  system/********@TEST_QA parfile=import_TEST.par Processing object type SCHEMA_EXPORT/USER Processing object type SCHEMA_EXPORT/SYSTEM_GRANT Processing object type SCHEMA_EXPORT/ROLE_GRANT Processing object type SCHEMA_EXPORT/DEFAULT_ROLE Pr
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det
7 comments
Read more

How to Create Pfile from Spfile and Vice Versa

<<Back to DB Administration Main Page There are instances when a DBA need to start the database using pfile, for example to trouble an instance startup error or to validate init file post parameter changes etc. In such situations you can create a pfile from spfile and once you are done with your changes you can create spfile from updated/modified pfile to start the database. How to Create Pfile from Spfile As sysdba execute following command  SQL> create pfile='/tmp/initOrcl.ora' from spfile; How to Create SPfile from Pfile As sysdba execute following command  SQL> create spfile from  pfile='/tmp/initOrcl.ora'; You can also create the pfile directly from memory How to Create Pfile from Memory As sysdba execute following command  SQL> create  pfile='/tmp/initOrcl.ora' from memory;
3 comments
Read more

How to export only data or only metadata using expdp

<<Back to Oracle DATAPUMP Main Page CONTENT parameter of expdp let you select whether you want to export only data or only metadata or both Default : ALL Syntax and Description CONTENT=[ALL | DATA_ONLY | METADATA_ONLY] DATA_ONLY exports only table row data; no database object definitions are exported. METADATA_ONLY exports only database object definitions; no table row data is exported. Exporting metadata only  $ cat exp_full_pdb01.par directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=METADATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par Exporting data only directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=DATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par
Post a Comment
Read more

Step by Step How to Configure Software Keystore/ Oracle Wallet

<<Back to Oracle DB Security Main Page How to Configure a Software Keystore A software keystore is a container that stores the Transparent Data Encryption master encryption key. To configure a software Keystore follow the steps below. Step 1: Set the Keystore Location in the sqlnet.ora File You can store the software keystore (also known as wallet) in file system or in ASM Diskgroup. Does not matter where you want to store the keystore you have modify the sqlnet.ora and make an entry accordingly Make an entry as shown below in $ORACLE_HOME/network/admin/sqlnet.ora file Example1: If Storing the Wallet in ASM ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= +DG_TST_DATA/$ORACLE_SID/wallet )    )  )   Example2: If Storing the Wallet in File System ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= /u01/dbatst1/admin/wallet/$ORACLE_SID)    )  ) NOTE: Ensure that the path you entered in  DIREC
7 comments
Read more

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i
2 comments
Read more

ORA-28365: wallet is not open while starting the database

<<Back to DB Administration Main Page ORA-28365: wallet is not open Encountered while Starting the Database $ srvctl start instance -d CDB001 -i CDB0011 PRCR-1013 : Failed to start resource ora.cdb001.db PRCR-1064 : Failed to start resource ora.cdb001.db on node node1.oracle.com CRS-5017: The resource action "ora.cdb001.db start" encountered the following error: ORA-28365: wallet is not open . For details refer to "(:CLSN00107:)" in "/u01/app/oracle/diag/crs/node1.oracle.com/crs/trace/crsd_oraagent_oracle.trc". CRS-2674: Start of 'ora.cdb001.db' on 'node1.oracle.com' failed Solution : Start the instance in mount mode SQL> startup mount; ORACLE instance started. Total System Global Area 2147483648 bytes Fixed Size                  2926472 bytes Variable Size            1392511096 bytes Database Buffers          738197504 bytes Redo Buffers               13848576 bytes Database mounted. Check Wallet status set linesiz
3 comments
Read more