RAC to Single Instance Standby Database Setup (Oracle 11gR2 Physical Standby)

#Oracle 官方建议，如果主节点是RAC+ASM，STANDBY 也建议使用ASM，这也是我们生产上使用较多的方式，STANDBY 使用 filesystem 也可以搭建出来，但是意义不大，无疑增加了管理难度。
下面是STANDBY使用ASM搭建过程：#


Primary is a 2 node-rac cluster with instances swx1 and swx2 running on ASM.
A service called swxscan is created for client sides. We will use this service name for the tnsnames.ora.
The standby instance will be called swxstandby and it will be running single instance on ASM as well.
This is a standard dataguard configuration but the only tricky part is the listeners on primary and DR, since in 11gR2 we have the Grid Infrastructure running under Grid user and RDBMS under oracle (provided you followed Oracle’s OFA, which by the way is the best way to do things imho)
Also take care for the user permissions on DR server for the raw devices. Since grid user owns the raw devices the group which grid is part of should also have oracle user as its member.
Do we will begin the procedure now. First we will do steps on Production RAC and then do the remaining on Standby server. I am not going to use active duplicate over the network. The reason for this is that in a production environment where size of your database is genereally above 500gb. If your bandwidth is not good enough it might take days to duplicate the database over network. Its better to use the old duplicate command and copy the rman backups over using a tape or any restore method at your disposal. What I do is backup it up to tape and then restore on DR site.
———————-
Environment
——————–
Primary Database 2 Node RAC
1 Node Names: swxracnode1, swxracnode2
2 DB Name: SWX
3 DB Unique Name: SWX
4 DB Version: 11.2.0.3
5 Grid Infrastructure (CRS + ASM).
6 SCAN settings in /etc/hosts file, so SCAN listener only running on one node (Swxracnode2 for this demo)
7 ASM Diskgroups: +DATA, +FRA
8 CRS installed with ‘Grid’ User, RDBMS installed with ‘Oracle’ user
Standby Database Single Instance:
1 ASM Diskgroup : +DATA, +FRA (For datafiles and FRA)
2 DB Unique Name: SWXSTANDBY
3 DB Name: SWX
4 CRS(for single instance) installed with ‘Grid’ User, RDBMS installed with ‘Oracle’ user
—————————
PREPARATIONS AT PRIMARY SITE
—————————-
GI_HOME= /grid/11.2.0/grid
ORACLE_HOME=/oracle/app/oracle/product/11.2.0/db_1
CRS User= Grid
RDBMS User= Oracle
1. Force logging on primary.
Login to any one node and run below sql command
alter database force logging;
2. Check for Online Redo Logfiles(ORL) on nodes and Create Standby Redo Logs (SRL) on the Primary RAC.
select * from gv$logfile;
select * from gv$log;
— ORL ADDITION —
Add atleast four groups per thread of size 100M;
ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 1 (‘+DATA/swx/onlinelog/redo-01-01.log’,’+DATA/swx/onlinelog/redo01-02.log’) SIZE 100m,
GROUP 2 (‘+DATA/swx/onlinelog/redo-02-01.log’,’+DATA/swx/onlinelog/redo-02-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 2
GROUP 3 (‘+DATA/swx/onlinelog/redo-03-01.log’,’+DATA/swx/onlinelog/redo-03-02.log’) SIZE 100m,
GROUP 4 (‘+DATA/swx/onlinelog/redo-04-01.log’,’+DATA/swx/onlinelog/redo-04-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 5 (‘+DATA/swx/onlinelog/redo-05-01.log’,’+DATA/swx/onlinelog/redo05-02.log’) SIZE 100m,
GROUP 6 (‘+DATA/swx/onlinelog/redo-06-01.log’,’+DATA/swx/onlinelog/redo-06-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 2
GROUP 7 (‘+DATA/swx/onlinelog/redo-07-01.log’,’+DATA/swx/onlinelog/redo-07-02.log’) SIZE 100m,
GROUP 8 (‘+DATA/swx/onlinelog/redo-08-01.log’,’+DATA/swx/onlinelog/redo-08-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 9 (‘+DATA/swx/onlinelog/redo-09-01.log’,’+DATA/swx/onlinelog/redo-09-02.log’) SIZE 100m,
GROUP 10 (‘+DATA/swx/onlinelog/redo-10-01.log’,’+DATA/swx/onlinelog/redo-10-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 2
GROUP 11 (‘+DATA/swx/onlinelog/redo-11-01.log’,’+DATA/swx/onlinelog/redo-11-02.log’) SIZE 100m,
GROUP 12 (‘+DATA/swx/onlinelog/redo-12-01.log’,’+DATA/swx/onlinelog/redo-12-02.log’) SIZE 100m;
Create Standby Redo Logs (SRL) related to the online redo log (ORL) files in the database. As there are three redo log groups with two members each we will create four members for each thread. Note that OMF (db_create_file_dest=’+DATA’) are used and the SRL are created with the same size as ORL.
(maximum # of logfiles +1) * maximum # of threads
For example in setup using two online log files for each thread. Thus, the number of standby redo logs should be (2 + 1) * 2 = 6. That is, one more standby redo log file for each thread.
3. Set DB_RECOVERY_FILE_DEST_SIZE, DB_RECOVERY_FILE_DEST and ADD the SRL’s
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE=400G scope=both sid=’*’;
SQL> alter system set DB_RECOVERY_FILE_DEST=’+FRA’ scope=both sid=’*’;
alter database add standby logfile thread 1 group 7 size 104857600;
alter database add standby logfile thread 1 group 8 size 104857600;
alter database add standby logfile thread 1 group 9 size 104857600;
alter database add standby logfile thread 1 group 10 size 104857600;
alter database add standby logfile thread 2 group 11 size 104857600;
alter database add standby logfile thread 2 group 12 size 104857600;
alter database add standby logfile thread 2 group 13 size 104857600;
alter database add standby logfile thread 2 group 14 size 104857600;
4. Bring Database in Archivelog mode
alter system set log_archive_dest_1=’location=+fra’ scope=both sid=’*’;
srvctl stop database -d swx
### log into both nodes
sqlplus “/as sysDBA”
startup mount
alter database archivelog;
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +FRA
Oldest online log sequence 1625
Next log sequence to archive 1626
Current log sequence 1626
SQL> alter database open;
5. Configure Listener.ora (GRID user) and Tnsnames.ora (ORACLE user) for both nodes on Primary Side
Configure tnsnames alias and a static registration with the GI listeners for both primary and standby database and compliant with Data Guard Broker. With Oracle 11gR2 since the SCAN Listener was introduced the modification is made to both listeners in GI $OH and to the tnsnames.ora in RDBMS $OH. Reload the listeners.
— Listener.ora on both Nodes of Primary RAC as Grid User–
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER))))
# line added by Agent
LISTENER_SCAN3=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_S
CAN3)))) # line added by Agent
LISTENER_SCAN2=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_S
CAN2)))) # line added by Agent
LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_S
CAN1)))) # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by
Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN2=ON # line added by
Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN3=ON # line added by
Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent
SWXSTANDBY =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby)
(SID_NAME = swxstandby)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx_DGMGRL)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby_DGMGRL)
(SID_NAME = swxstandby)
)
)
## As grid user in $ORACLE_HOME (which is the Grid Home) do the below on both nodes.Start and Stop all scan listeners on both nodes
lsnrctl stop LISTENER_SCAN1
lsnrctl stop LISTENER_SCAN2
lsnrctl stop LISTENER_SCAN3
lsnrctl start LISTENER_SCAN1
lsnrctl start LISTENER_SCAN2
lsnrctl start LISTENER_SCAN3
— TNSNAMES.ora on both Nodes of Primary RAC as Oracle user —
SWXSTANDBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swxstandby)
)
)
SWX =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxscan)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swx)
)
)
## tnsping ping swx, swxstandby as Oracle user to check ### If not pingabe check if DNS is configured on your server

6. Create password files for the Nodes as Oracle user.
User format as orapwswx1 for node 1
User format as orapwswx2 for node 2
Create the password file in folder $ORACLE_HOME/dbs on all nodes.
orapwd file=$ORACLE_HOME/dbs/orapwsswx1 ignorecase=y password=xxxxxxxx force=y
orapwd file=$ORACLE_HOME/dbs/orapwsswx2 ignorecase=y password=xxxxxxxx force=y
–ignore case is important parameter here since from 11gR2 onwards passwords are case-sensitive
PING[ARC2]: Heartbeat failed to connect to standby ‘swx’. Error is 16191.
Error 1017 received logging on to the standby
These are common errors associated with password files. If you encounter the above errors, recreate the password files.

7. Create initialization parameter file and add Standby database parameters to it.
We will not use Active duplication over the network. Since in a production environment it is sometimes impractical; where size of database can easily exceed 1TB. The method to duplicate via RMAN and copy the backup to Standby database server is a tried and tested method and works beautifully.
Login to sqlplus on one of the nodes.
show parameter spfile;
create pfile=’/backup/swxPRIMARY.ora’ from spfile;
Ensure you remote_listener parameter is set to your scan listener
*.remote_listener=’swxscan.domain.com:1521′
Add the below parameters to the new swxPRIMARY.ora file

#########################PRIMARY PARAMETERS########################
*.DB_UNIQUE_NAME=’swx’
*.db_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swx’
*.log_archive_dest_2=’service=swxstandby LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swxstandby’
*.LOG_ARCHIVE_DEST_STATE_1=’ENABLE’
*.LOG_ARCHIVE_DEST_STATE_2=’ENABLE’
*.LOG_ARCHIVE_FORMAT=’log%t_%s_%r.arc’
*.log_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.remote_login_passwordfile=’exclusive’
*.STANDBY_FILE_MANAGEMENT=’AUTO’
*.fal_client=’SWX’
*.fal_server=’SWXSTANDBY’
*.sec_case_sensitive_logon=FALSE


########################################
FULL PARAMETER FILE OF THE PRIMARY DATABASE
swx2.__db_cache_size=4294967296
swx1.__db_cache_size=3892314112
swx2.__java_pool_size=16777216
swx1.__java_pool_size=33554432
swx2.__large_pool_size=33554432
swx1.__large_pool_size=50331648
swx2.__pga_aggregate_target=2147483648
swx1.__pga_aggregate_target=2147483648
swx2.__sga_target=6442450944
swx1.__sga_target=6442450944
swx2.__shared_io_pool_size=536870912
swx1.__shared_io_pool_size=536870912
swx2.__shared_pool_size=1526726656
swx1.__shared_pool_size=1862270976
swx2.__streams_pool_size=0
swx1.__streams_pool_size=33554432
*.audit_file_dest=’/oracle/app/oracle/admin/swx/adump’
*.audit_trail=’db’
*.cluster_database=true
*.compatible=’11.2.0.0.0′
*.control_files=’+DATA/swx/controlfile/current.265.773009443′
*.db_block_size=8192
*.db_create_file_dest=’+DATA’
*.db_domain=”
*.db_name=’swx’
*.db_recovery_file_dest_size=429496729600
*.db_recovery_file_dest=’+FRA’
*.diagnostic_dest=’/oracle/app/oracle’
*.dispatchers='(PROTOCOL=TCP) (SERVICE=swxXDB)’
*.swx1.instance_number=1
*.swx2.instance_number=2
*.job_queue_processes=1000
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swx’
*.log_archive_dest_2=’service=swxstandby LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swxstandby’
*.open_cursors=300
*.pga_aggregate_target=2147483648
*.processes=1000
*.remote_listener=’swxscan.qiibonline.com:1521′
*.remote_login_passwordfile=’exclusive’
*.sessions=1105
*.sga_target=6442450944
*.standby_file_management=’AUTO’
*.swx2.thread=2
*.swx1.thread=1
*.swx2.undo_tablespace=’UNDOTBS2′
*.swx1.undo_tablespace=’UNDOTBS1′
*.db_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.log_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.standby_file_management=auto
*.fal_server=’SWXSTANDBY’
*.fal_client=’SWX’
Bounce the database with the new parameter file
sqlplus “/as sysdba”
shutdown immediate;
— shutdown 2nd node also, you can use ‘srvctl stop database -d swx’ for this also
startup pfile=’/backup/swxPRIMARY.ora’;
create spfile from pfile=’/backup/swxPRIMARY.ora’;
shutdown immediate;
startup;
show parameter spfile;
Now we have completed the steps at Primary Side, only the duplicate command from RMAN is remaining. But let us first ensure we prepare the standby database before we duplicate and restore the database.
—————————
PREPARATIONS AT STANDBY SITE
—————————-
GI_HOME= /grid/11.2.0/grid
ORACLE_HOME=/oracle/app/oracle/product/11.2.0/db_1
CRS User= Grid
RDBMS User= Oracle
The installation for database is grid infrastrcuture utilizing ASM for the database. We have already created the HAS services and the RDBMS software was also installed. In ASM 2 diskgroups called +DATA, +FRA was created, same like production.
We will create a new database using the intialization parameter file we created before but we will add new parameters for the standby database. If your are doing this setup on windows then you will have to create a windows service first using ‘oradim’
1. Create listener.ora with Grid user
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
)
ADR_BASE_LISTENER = /grid/app
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent
SWXSTANDBY =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby)
(SID_NAME = swxstandby)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx_DGMGRL)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby_DGMGRL)
(SID_NAME = swxstandby)
)
)
Reload the listeners using lsnrctl reload command
2. Create tnsnames.ora file using Oracle user
SWX =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxscan.domain.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swx)
)
)
SWXSTANDBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr.domain.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swxstandby)
)
)
3. Create Directory for adump audit_file_dest, also create directories in the ASM diskgroup using ASMCMD
— as oracle user —
mkdir -p /oracle/app/oracle/admin/swx/adump
asmcmd>
asmcmd> mkdir +DATA/SWXSTANDBY/
asmcmd> mkdir +DATA/SWX/
asmcmd> mkdir +FRA/SWXSTANDBY/
asmcmd> mkdir +FRA/SWX/
Also create any other directories you think you have missed in ASM or on the local filesystem.


4. Change intilization parameters in swxPRIMARY.ora file and name file as swxSTANDBY.ora
Since it is RAC to single instance dataguard the parameter cluster_database needs to be set to false. This is the primary difference between a single instance and a rac database.
#########################STANDBY DATABASE PARAMETERS########################
*.DB_UNIQUE_NAME=’SWXSTANDBY’
*.db_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swxstandby’
*.log_archive_dest_2=’service=swx LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swx’
*.LOG_ARCHIVE_DEST_STATE_1=’ENABLE’
*.LOG_ARCHIVE_DEST_STATE_2=’ENABLE’
*.LOG_ARCHIVE_FORMAT=’log%t_%s_%r.arc’
*.log_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.remote_login_passwordfile=’exclusive’
*.STANDBY_FILE_MANAGEMENT=’AUTO’
*.fal_client=’SWXSTANDBY’
*.fal_server=’SWX’
*.cluster_database=false
*.sec_case_sensitive_logon=FALSE
########################################
FULL PARAMETER FILE swxSTANDBY.ora
swxstandby.__db_cache_size=3724541952
swxstandby.__java_pool_size=16777216
swxstandby.__large_pool_size=50331648
swxstandby.__pga_aggregate_target=2147483648
swxstandby.__sga_target=6442450944
swxstandby.__shared_io_pool_size=536870912
swxstandby.__shared_pool_size=2063597568
swxstandby.__streams_pool_size=16777216
*.audit_file_dest=’/oracle/app/oracle/admin/swx/adump’
*.cluster_database=false
*.compatible=’11.2.0.0.0′
*.control_files=’+DATA/swxstandby/controlfile/current.272.792584487’#Restore Controlfile
*.db_block_size=8192
*.db_create_file_dest=’+DATA’
*.db_create_online_log_dest_1=’+FRA’
*.db_domain=”
*.db_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.db_name=’swx’
*.db_recovery_file_dest_size=429496729600
*.db_recovery_file_dest=’+FRA’
*.db_unique_name=’SWXSTANDBY’
*.diagnostic_dest=’/oracle/app/oracle’
*.dispatchers='(PROTOCOL=TCP) (SERVICE=swxXDB)’
*.fal_client=’SWXSTANDBY’
*.fal_server=’SWX’
*.job_queue_processes=1000
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swxstandby’
*.log_archive_dest_2=’service=swx LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swx’
*.log_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.open_cursors=300
*.pga_aggregate_target=2147483648
*.processes=1000
*.remote_listener=’swxscan.qiibonline.com:1521′
*.remote_login_passwordfile=’exclusive’
*.sec_case_sensitive_logon=FALSE
*.sessions=1105
*.sga_target=6442450944
*.standby_file_management=’AUTO’
*.undo_tablespace=’UNDOTBS1′
5. Now startup the database in nomount mode using this pfile and create spfile from it.
sqlplus “/as sysdba”
startup nomount pfile=’/backup/swxSTANDBY.ora’;
create spfile from pfile=’/backup/swxSTANDBY.ora’;
shutdown immediate;
startup nomount;
6. Create password file for standby database
Create the password file in folder $ORACLE_HOME/dbs on all nodes and DR server as Oracle user
User format as orapwswxstandby for Standby database
orapwd file=$ORACLE_HOME/dbs/orapwswxstandby force=y ignorecase=y password=xxxxxx
To check password file use query from sql plus.
select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
—————————— —– —– —–
SYS TRUE TRUE FALSE
—————————
DUPLICATING THE DATABASE FOR STANDBY FROM RMAN
—————————-
1. Before duplicating ensure that the mountpoint /backup exists on the DR server. This is the location where we will copy the backups to and restore from there.
RMAN > show all;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ‘/backup/rmanbkp/SWX_Lev0_%s_%D_%M_%Y’;
RMAN> sql ‘alter system archive log current’;
RMAN> backup database include current controlfile for standby plus archivelog;
Copy the database to the DR server on folder ‘/backup/rmanbkp’ and now we will begin to duplicate
Login to RMAN from DR server from Oracle user like below
rman target sys/***@swx auxiliary sys/***
or
rman target sys/***@swx auxiliary /
or
rman target sys/***@swx auxiliary sys/****@swxstandby
$ rman target sys/*****@swx auxiliary /
Recovery Manager: Release 11.2.0.3.0 – Production on Tue Nov 20 15:39:01 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SWX (DBID=xxxxxx)
connected to auxiliary database: SWX (DBID=xxxxxx)
If you get some error use (UR=A) in tnsnames.ora file like
(SERVICE_NAME = swx) (UR=A)
Go to primary server and crosscheck archivelogs and backupsets and delete expired or obsolete objects and relogin to auxiliary.
RMAN> duplicate target database for standby nofilenamecheck dorecover;
2. Put the Standby into Managed standby mode:
ON standby server
shutdown immediate;
alter database mount standby database;
alter database recover managed standby database using current logfile disconnect from session;
Go to the Primary Server:
SQL> alter system switch logfile;
SQL> alter system archive log current;
Check if the logs are coming here and properly applying.
3. Verify the sync between primary and standby
From primary
sql > select max(sequence#) as “PRIMARY” from v$log_history;
From Standby
SQL > select max(sequence#) as “STANDBY”,applied from v$archived_log group by applied ;
SQL> Select process,status from v$managed_standby;
If there is error like below , it is generally due to password files and for 11gR2 the parameter sec_case_sensitive_logon
PING[ARC2]: Heartbeat failed to connect to standby ” Error is 16191.
Error 1017 received logging on to the standby
Recreate the password files and alter sec_case_sensitive_logon to false
Invoking a DR Standby Database
Overview
There are different methods you can use to invoke a standby database depending on the typical DR scenario you are facing.
Scenario for usage.
1. Database Switchover
Using this method you can switch backwards and forwards between the primary and DR servers (e.g. so that the primary can become DR and DR can become primary) without having to rebuild either environment.
This scenario can be used if both the Primary and Standby Servers are available so that you can connect to both environments simultaneously and perform a clean switchover.
2. Activating a Standby Database
This method will activate the Standby Database as the primary database recovering up to the point of the last log shipment. After activating a standby database as the primary the original primary server becomes obsolete and will need to be rebuilt as a standby database (e.g. you can not just switch the servers back to act as a primary or standby database and will need to rebuild the data-guard environments).
This scenario can be used if the primary server is not available and you need to force the standby database to become the primary.
3. Opening the standby Database in Read-Only Mode
This method involves stopping data-guard replication and opening the standby database in read-only mode for querying. The database can then be shutdown and reopened in standby mode so that data-guard replication can resume (assuming all required archive logs are still available)
This scenario can be used if you want to open the standby database temporarily for querying data and then wish to put the database back into standby mode.
The following section describes how to perform each of the above methods of invoking a standby database:
1. Database Switchover
Using this method you can switch backwards and forwards between the primary and DR servers (e.g. so that the primary can become DR and DR can become primary) without having to rebuild either environment:
On Primary Server:
SQL> alter database commit to switchover to standby;
This may cause the following error to be generated:
ERROR at line 1:
ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected
If this does occur then restart the database, as below, before retrying the above command:
SQL> shutdown immediate
SQL> startup
SQL> shutdown immediate
SQL> startup nomount
SQL> alter database mount standby database;
SQL> alter database recover managed standby database disconnect;
The primary server is now configured as a DR standby database.
On DR Server:
SQL> alter database recover managed standby database cancel;
SQL> alter database commit to switchover to primary;
SQL> shutdown immediate
SQL> startup
The DR server is now configured as the primary database.
To switch back you just need to repeat the above process but the other way around (e.g. convert the DR database back to a standby and the primary database back to primary).
2. Activating a Standby Database
If the primary database is not available the standby database can be converted into the primary database as follows:
SQL> alter database recover managed standby database cancel;
SQL> alter database activate standby database;
SQL> shutdown immediate
SQL> startup
The original primary database is now obsolete and can be rebuilt as a standby database once it is available again.
3. Opening the Standby Database in Read Only Mode (Active Dataguard)
The standby database can be opened in read only mode for querying and then converted back into a standby database without affecting the primary.
On standby server:
SQL> alter database recover managed standby database cancel;
SQL> alter database open read only;
The standby database is now open and available for querying in read only mode.
To put the standby database back into standby mode:
SQL> shutdown immediate
SQL> startup nomount
SQL> alter database mount standby database;
SQL> alter database recover managed standby database disconnect;

RAC to Single Instance Standby Database Setup (Oracle 11gR2 Physical Standby)

#Oracle 官方建议，如果主节点是RAC+ASM，STANDBY 也建议使用ASM，这也是我们生产上使用较多的方式，STANDBY 使用 filesystem 也可以搭建出来，但是意义不大，无疑增加了管理难度。
下面是STANDBY使用ASM搭建过程：#


Primary is a 2 node-rac cluster with instances swx1 and swx2 running on ASM.
A service called swxscan is created for client sides. We will use this service name for the tnsnames.ora.
The standby instance will be called swxstandby and it will be running single instance on ASM as well.
This is a standard dataguard configuration but the only tricky part is the listeners on primary and DR, since in 11gR2 we have the Grid Infrastructure running under Grid user and RDBMS under oracle (provided you followed Oracle’s OFA, which by the way is the best way to do things imho)
Also take care for the user permissions on DR server for the raw devices. Since grid user owns the raw devices the group which grid is part of should also have oracle user as its member.
Do we will begin the procedure now. First we will do steps on Production RAC and then do the remaining on Standby server. I am not going to use active duplicate over the network. The reason for this is that in a production environment where size of your database is genereally above 500gb. If your bandwidth is not good enough it might take days to duplicate the database over network. Its better to use the old duplicate command and copy the rman backups over using a tape or any restore method at your disposal. What I do is backup it up to tape and then restore on DR site.
———————-
Environment
——————–
Primary Database 2 Node RAC
1 Node Names: swxracnode1, swxracnode2
2 DB Name: SWX
3 DB Unique Name: SWX
4 DB Version: 11.2.0.3
5 Grid Infrastructure (CRS + ASM).
6 SCAN settings in /etc/hosts file, so SCAN listener only running on one node (Swxracnode2 for this demo)
7 ASM Diskgroups: +DATA, +FRA
8 CRS installed with ‘Grid’ User, RDBMS installed with ‘Oracle’ user
Standby Database Single Instance:
1 ASM Diskgroup : +DATA, +FRA (For datafiles and FRA)
2 DB Unique Name: SWXSTANDBY
3 DB Name: SWX
4 CRS(for single instance) installed with ‘Grid’ User, RDBMS installed with ‘Oracle’ user
—————————
PREPARATIONS AT PRIMARY SITE
—————————-
GI_HOME= /grid/11.2.0/grid
ORACLE_HOME=/oracle/app/oracle/product/11.2.0/db_1
CRS User= Grid
RDBMS User= Oracle
1. Force logging on primary.
Login to any one node and run below sql command
alter database force logging;
2. Check for Online Redo Logfiles(ORL) on nodes and Create Standby Redo Logs (SRL) on the Primary RAC.
select * from gv$logfile;
select * from gv$log;
— ORL ADDITION —
Add atleast four groups per thread of size 100M;
ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 1 (‘+DATA/swx/onlinelog/redo-01-01.log’,’+DATA/swx/onlinelog/redo01-02.log’) SIZE 100m,
GROUP 2 (‘+DATA/swx/onlinelog/redo-02-01.log’,’+DATA/swx/onlinelog/redo-02-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 2
GROUP 3 (‘+DATA/swx/onlinelog/redo-03-01.log’,’+DATA/swx/onlinelog/redo-03-02.log’) SIZE 100m,
GROUP 4 (‘+DATA/swx/onlinelog/redo-04-01.log’,’+DATA/swx/onlinelog/redo-04-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 5 (‘+DATA/swx/onlinelog/redo-05-01.log’,’+DATA/swx/onlinelog/redo05-02.log’) SIZE 100m,
GROUP 6 (‘+DATA/swx/onlinelog/redo-06-01.log’,’+DATA/swx/onlinelog/redo-06-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 2
GROUP 7 (‘+DATA/swx/onlinelog/redo-07-01.log’,’+DATA/swx/onlinelog/redo-07-02.log’) SIZE 100m,
GROUP 8 (‘+DATA/swx/onlinelog/redo-08-01.log’,’+DATA/swx/onlinelog/redo-08-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 9 (‘+DATA/swx/onlinelog/redo-09-01.log’,’+DATA/swx/onlinelog/redo-09-02.log’) SIZE 100m,
GROUP 10 (‘+DATA/swx/onlinelog/redo-10-01.log’,’+DATA/swx/onlinelog/redo-10-02.log’) SIZE 100m;
ALTER DATABASE ADD LOGFILE THREAD 2
GROUP 11 (‘+DATA/swx/onlinelog/redo-11-01.log’,’+DATA/swx/onlinelog/redo-11-02.log’) SIZE 100m,
GROUP 12 (‘+DATA/swx/onlinelog/redo-12-01.log’,’+DATA/swx/onlinelog/redo-12-02.log’) SIZE 100m;
Create Standby Redo Logs (SRL) related to the online redo log (ORL) files in the database. As there are three redo log groups with two members each we will create four members for each thread. Note that OMF (db_create_file_dest=’+DATA’) are used and the SRL are created with the same size as ORL.
(maximum # of logfiles +1) * maximum # of threads
For example in setup using two online log files for each thread. Thus, the number of standby redo logs should be (2 + 1) * 2 = 6. That is, one more standby redo log file for each thread.
3. Set DB_RECOVERY_FILE_DEST_SIZE, DB_RECOVERY_FILE_DEST and ADD the SRL’s
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE=400G scope=both sid=’*’;
SQL> alter system set DB_RECOVERY_FILE_DEST=’+FRA’ scope=both sid=’*’;
alter database add standby logfile thread 1 group 7 size 104857600;
alter database add standby logfile thread 1 group 8 size 104857600;
alter database add standby logfile thread 1 group 9 size 104857600;
alter database add standby logfile thread 1 group 10 size 104857600;
alter database add standby logfile thread 2 group 11 size 104857600;
alter database add standby logfile thread 2 group 12 size 104857600;
alter database add standby logfile thread 2 group 13 size 104857600;
alter database add standby logfile thread 2 group 14 size 104857600;
4. Bring Database in Archivelog mode
alter system set log_archive_dest_1=’location=+fra’ scope=both sid=’*’;
srvctl stop database -d swx
### log into both nodes
sqlplus “/as sysDBA”
startup mount
alter database archivelog;
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +FRA
Oldest online log sequence 1625
Next log sequence to archive 1626
Current log sequence 1626
SQL> alter database open;
5. Configure Listener.ora (GRID user) and Tnsnames.ora (ORACLE user) for both nodes on Primary Side
Configure tnsnames alias and a static registration with the GI listeners for both primary and standby database and compliant with Data Guard Broker. With Oracle 11gR2 since the SCAN Listener was introduced the modification is made to both listeners in GI $OH and to the tnsnames.ora in RDBMS $OH. Reload the listeners.
— Listener.ora on both Nodes of Primary RAC as Grid User–
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER))))
# line added by Agent
LISTENER_SCAN3=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_S
CAN3)))) # line added by Agent
LISTENER_SCAN2=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_S
CAN2)))) # line added by Agent
LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_S
CAN1)))) # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by
Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN2=ON # line added by
Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN3=ON # line added by
Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent
SWXSTANDBY =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby)
(SID_NAME = swxstandby)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx_DGMGRL)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby_DGMGRL)
(SID_NAME = swxstandby)
)
)
## As grid user in $ORACLE_HOME (which is the Grid Home) do the below on both nodes.Start and Stop all scan listeners on both nodes
lsnrctl stop LISTENER_SCAN1
lsnrctl stop LISTENER_SCAN2
lsnrctl stop LISTENER_SCAN3
lsnrctl start LISTENER_SCAN1
lsnrctl start LISTENER_SCAN2
lsnrctl start LISTENER_SCAN3
— TNSNAMES.ora on both Nodes of Primary RAC as Oracle user —
SWXSTANDBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swxstandby)
)
)
SWX =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxscan)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swx)
)
)
## tnsping ping swx, swxstandby as Oracle user to check ### If not pingabe check if DNS is configured on your server

6. Create password files for the Nodes as Oracle user.
User format as orapwswx1 for node 1
User format as orapwswx2 for node 2
Create the password file in folder $ORACLE_HOME/dbs on all nodes.
orapwd file=$ORACLE_HOME/dbs/orapwsswx1 ignorecase=y password=xxxxxxxx force=y
orapwd file=$ORACLE_HOME/dbs/orapwsswx2 ignorecase=y password=xxxxxxxx force=y
–ignore case is important parameter here since from 11gR2 onwards passwords are case-sensitive
PING[ARC2]: Heartbeat failed to connect to standby ‘swx’. Error is 16191.
Error 1017 received logging on to the standby
These are common errors associated with password files. If you encounter the above errors, recreate the password files.

7. Create initialization parameter file and add Standby database parameters to it.
We will not use Active duplication over the network. Since in a production environment it is sometimes impractical; where size of database can easily exceed 1TB. The method to duplicate via RMAN and copy the backup to Standby database server is a tried and tested method and works beautifully.
Login to sqlplus on one of the nodes.
show parameter spfile;
create pfile=’/backup/swxPRIMARY.ora’ from spfile;
Ensure you remote_listener parameter is set to your scan listener
*.remote_listener=’swxscan.domain.com:1521′
Add the below parameters to the new swxPRIMARY.ora file

#########################PRIMARY PARAMETERS########################
*.DB_UNIQUE_NAME=’swx’
*.db_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swx’
*.log_archive_dest_2=’service=swxstandby LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swxstandby’
*.LOG_ARCHIVE_DEST_STATE_1=’ENABLE’
*.LOG_ARCHIVE_DEST_STATE_2=’ENABLE’
*.LOG_ARCHIVE_FORMAT=’log%t_%s_%r.arc’
*.log_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.remote_login_passwordfile=’exclusive’
*.STANDBY_FILE_MANAGEMENT=’AUTO’
*.fal_client=’SWX’
*.fal_server=’SWXSTANDBY’
*.sec_case_sensitive_logon=FALSE


########################################
FULL PARAMETER FILE OF THE PRIMARY DATABASE
swx2.__db_cache_size=4294967296
swx1.__db_cache_size=3892314112
swx2.__java_pool_size=16777216
swx1.__java_pool_size=33554432
swx2.__large_pool_size=33554432
swx1.__large_pool_size=50331648
swx2.__pga_aggregate_target=2147483648
swx1.__pga_aggregate_target=2147483648
swx2.__sga_target=6442450944
swx1.__sga_target=6442450944
swx2.__shared_io_pool_size=536870912
swx1.__shared_io_pool_size=536870912
swx2.__shared_pool_size=1526726656
swx1.__shared_pool_size=1862270976
swx2.__streams_pool_size=0
swx1.__streams_pool_size=33554432
*.audit_file_dest=’/oracle/app/oracle/admin/swx/adump’
*.audit_trail=’db’
*.cluster_database=true
*.compatible=’11.2.0.0.0′
*.control_files=’+DATA/swx/controlfile/current.265.773009443′
*.db_block_size=8192
*.db_create_file_dest=’+DATA’
*.db_domain=”
*.db_name=’swx’
*.db_recovery_file_dest_size=429496729600
*.db_recovery_file_dest=’+FRA’
*.diagnostic_dest=’/oracle/app/oracle’
*.dispatchers='(PROTOCOL=TCP) (SERVICE=swxXDB)’
*.swx1.instance_number=1
*.swx2.instance_number=2
*.job_queue_processes=1000
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swx’
*.log_archive_dest_2=’service=swxstandby LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swxstandby’
*.open_cursors=300
*.pga_aggregate_target=2147483648
*.processes=1000
*.remote_listener=’swxscan.qiibonline.com:1521′
*.remote_login_passwordfile=’exclusive’
*.sessions=1105
*.sga_target=6442450944
*.standby_file_management=’AUTO’
*.swx2.thread=2
*.swx1.thread=1
*.swx2.undo_tablespace=’UNDOTBS2′
*.swx1.undo_tablespace=’UNDOTBS1′
*.db_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.log_file_name_convert=’+DATA/SWXSTANDBY/’,’+DATA/SWX/’,’+FRA/SWXSTANDBY/’,’+FRA/SWX/’
*.standby_file_management=auto
*.fal_server=’SWXSTANDBY’
*.fal_client=’SWX’
Bounce the database with the new parameter file
sqlplus “/as sysdba”
shutdown immediate;
— shutdown 2nd node also, you can use ‘srvctl stop database -d swx’ for this also
startup pfile=’/backup/swxPRIMARY.ora’;
create spfile from pfile=’/backup/swxPRIMARY.ora’;
shutdown immediate;
startup;
show parameter spfile;
Now we have completed the steps at Primary Side, only the duplicate command from RMAN is remaining. But let us first ensure we prepare the standby database before we duplicate and restore the database.
—————————
PREPARATIONS AT STANDBY SITE
—————————-
GI_HOME= /grid/11.2.0/grid
ORACLE_HOME=/oracle/app/oracle/product/11.2.0/db_1
CRS User= Grid
RDBMS User= Oracle
The installation for database is grid infrastrcuture utilizing ASM for the database. We have already created the HAS services and the RDBMS software was also installed. In ASM 2 diskgroups called +DATA, +FRA was created, same like production.
We will create a new database using the intialization parameter file we created before but we will add new parameters for the standby database. If your are doing this setup on windows then you will have to create a windows service first using ‘oradim’
1. Create listener.ora with Grid user
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
)
ADR_BASE_LISTENER = /grid/app
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by Agent
SWXSTANDBY =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr)(PORT = 1521))
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby)
(SID_NAME = swxstandby)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swx_DGMGRL)
(SID_NAME = swx)
)
(SID_DESC =
(ORACLE_HOME= /grid/11.2.0/grid)
(GLOBAL_DBNAME = swxstandby_DGMGRL)
(SID_NAME = swxstandby)
)
)
Reload the listeners using lsnrctl reload command
2. Create tnsnames.ora file using Oracle user
SWX =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxscan.domain.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swx)
)
)
SWXSTANDBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = swxracdr.domain.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = swxstandby)
)
)
3. Create Directory for adump audit_file_dest, also create directories in the ASM diskgroup using ASMCMD
— as oracle user —
mkdir -p /oracle/app/oracle/admin/swx/adump
asmcmd>
asmcmd> mkdir +DATA/SWXSTANDBY/
asmcmd> mkdir +DATA/SWX/
asmcmd> mkdir +FRA/SWXSTANDBY/
asmcmd> mkdir +FRA/SWX/
Also create any other directories you think you have missed in ASM or on the local filesystem.


4. Change intilization parameters in swxPRIMARY.ora file and name file as swxSTANDBY.ora
Since it is RAC to single instance dataguard the parameter cluster_database needs to be set to false. This is the primary difference between a single instance and a rac database.
#########################STANDBY DATABASE PARAMETERS########################
*.DB_UNIQUE_NAME=’SWXSTANDBY’
*.db_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swxstandby’
*.log_archive_dest_2=’service=swx LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swx’
*.LOG_ARCHIVE_DEST_STATE_1=’ENABLE’
*.LOG_ARCHIVE_DEST_STATE_2=’ENABLE’
*.LOG_ARCHIVE_FORMAT=’log%t_%s_%r.arc’
*.log_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.remote_login_passwordfile=’exclusive’
*.STANDBY_FILE_MANAGEMENT=’AUTO’
*.fal_client=’SWXSTANDBY’
*.fal_server=’SWX’
*.cluster_database=false
*.sec_case_sensitive_logon=FALSE
########################################
FULL PARAMETER FILE swxSTANDBY.ora
swxstandby.__db_cache_size=3724541952
swxstandby.__java_pool_size=16777216
swxstandby.__large_pool_size=50331648
swxstandby.__pga_aggregate_target=2147483648
swxstandby.__sga_target=6442450944
swxstandby.__shared_io_pool_size=536870912
swxstandby.__shared_pool_size=2063597568
swxstandby.__streams_pool_size=16777216
*.audit_file_dest=’/oracle/app/oracle/admin/swx/adump’
*.cluster_database=false
*.compatible=’11.2.0.0.0′
*.control_files=’+DATA/swxstandby/controlfile/current.272.792584487’#Restore Controlfile
*.db_block_size=8192
*.db_create_file_dest=’+DATA’
*.db_create_online_log_dest_1=’+FRA’
*.db_domain=”
*.db_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.db_name=’swx’
*.db_recovery_file_dest_size=429496729600
*.db_recovery_file_dest=’+FRA’
*.db_unique_name=’SWXSTANDBY’
*.diagnostic_dest=’/oracle/app/oracle’
*.dispatchers='(PROTOCOL=TCP) (SERVICE=swxXDB)’
*.fal_client=’SWXSTANDBY’
*.fal_server=’SWX’
*.job_queue_processes=1000
*.log_archive_config=’dg_config=(swxstandby,swx)’
*.log_archive_dest_1=’LOCATION=+FRA valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=swxstandby’
*.log_archive_dest_2=’service=swx LGWR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=swx’
*.log_file_name_convert=’+DATA/SWX/’,’+DATA/SWXSTANDBY/’,’+FRA/SWX/’,’+FRA/SWXSTANDBY/’
*.open_cursors=300
*.pga_aggregate_target=2147483648
*.processes=1000
*.remote_listener=’swxscan.qiibonline.com:1521′
*.remote_login_passwordfile=’exclusive’
*.sec_case_sensitive_logon=FALSE
*.sessions=1105
*.sga_target=6442450944
*.standby_file_management=’AUTO’
*.undo_tablespace=’UNDOTBS1′
5. Now startup the database in nomount mode using this pfile and create spfile from it.
sqlplus “/as sysdba”
startup nomount pfile=’/backup/swxSTANDBY.ora’;
create spfile from pfile=’/backup/swxSTANDBY.ora’;
shutdown immediate;
startup nomount;
6. Create password file for standby database
Create the password file in folder $ORACLE_HOME/dbs on all nodes and DR server as Oracle user
User format as orapwswxstandby for Standby database
orapwd file=$ORACLE_HOME/dbs/orapwswxstandby force=y ignorecase=y password=xxxxxx
To check password file use query from sql plus.
select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
—————————— —– —– —–
SYS TRUE TRUE FALSE
—————————
DUPLICATING THE DATABASE FOR STANDBY FROM RMAN
—————————-
1. Before duplicating ensure that the mountpoint /backup exists on the DR server. This is the location where we will copy the backups to and restore from there.
RMAN > show all;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ‘/backup/rmanbkp/SWX_Lev0_%s_%D_%M_%Y’;
RMAN> sql ‘alter system archive log current’;
RMAN> backup database include current controlfile for standby plus archivelog;
Copy the database to the DR server on folder ‘/backup/rmanbkp’ and now we will begin to duplicate
Login to RMAN from DR server from Oracle user like below
rman target sys/***@swx auxiliary sys/***
or
rman target sys/***@swx auxiliary /
or
rman target sys/***@swx auxiliary sys/****@swxstandby
$ rman target sys/*****@swx auxiliary /
Recovery Manager: Release 11.2.0.3.0 – Production on Tue Nov 20 15:39:01 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SWX (DBID=xxxxxx)
connected to auxiliary database: SWX (DBID=xxxxxx)
If you get some error use (UR=A) in tnsnames.ora file like
(SERVICE_NAME = swx) (UR=A)
Go to primary server and crosscheck archivelogs and backupsets and delete expired or obsolete objects and relogin to auxiliary.
RMAN> duplicate target database for standby nofilenamecheck dorecover;
2. Put the Standby into Managed standby mode:
ON standby server
shutdown immediate;
alter database mount standby database;
alter database recover managed standby database using current logfile disconnect from session;
Go to the Primary Server:
SQL> alter system switch logfile;
SQL> alter system archive log current;
Check if the logs are coming here and properly applying.
3. Verify the sync between primary and standby
From primary
sql > select max(sequence#) as “PRIMARY” from v$log_history;
From Standby
SQL > select max(sequence#) as “STANDBY”,applied from v$archived_log group by applied ;
SQL> Select process,status from v$managed_standby;
If there is error like below , it is generally due to password files and for 11gR2 the parameter sec_case_sensitive_logon
PING[ARC2]: Heartbeat failed to connect to standby ” Error is 16191.
Error 1017 received logging on to the standby
Recreate the password files and alter sec_case_sensitive_logon to false
Invoking a DR Standby Database
Overview
There are different methods you can use to invoke a standby database depending on the typical DR scenario you are facing.
Scenario for usage.
1. Database Switchover
Using this method you can switch backwards and forwards between the primary and DR servers (e.g. so that the primary can become DR and DR can become primary) without having to rebuild either environment.
This scenario can be used if both the Primary and Standby Servers are available so that you can connect to both environments simultaneously and perform a clean switchover.
2. Activating a Standby Database
This method will activate the Standby Database as the primary database recovering up to the point of the last log shipment. After activating a standby database as the primary the original primary server becomes obsolete and will need to be rebuilt as a standby database (e.g. you can not just switch the servers back to act as a primary or standby database and will need to rebuild the data-guard environments).
This scenario can be used if the primary server is not available and you need to force the standby database to become the primary.
3. Opening the standby Database in Read-Only Mode
This method involves stopping data-guard replication and opening the standby database in read-only mode for querying. The database can then be shutdown and reopened in standby mode so that data-guard replication can resume (assuming all required archive logs are still available)
This scenario can be used if you want to open the standby database temporarily for querying data and then wish to put the database back into standby mode.
The following section describes how to perform each of the above methods of invoking a standby database:
1. Database Switchover
Using this method you can switch backwards and forwards between the primary and DR servers (e.g. so that the primary can become DR and DR can become primary) without having to rebuild either environment:
On Primary Server:
SQL> alter database commit to switchover to standby;
This may cause the following error to be generated:
ERROR at line 1:
ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected
If this does occur then restart the database, as below, before retrying the above command:
SQL> shutdown immediate
SQL> startup
SQL> shutdown immediate
SQL> startup nomount
SQL> alter database mount standby database;
SQL> alter database recover managed standby database disconnect;
The primary server is now configured as a DR standby database.
On DR Server:
SQL> alter database recover managed standby database cancel;
SQL> alter database commit to switchover to primary;
SQL> shutdown immediate
SQL> startup
The DR server is now configured as the primary database.
To switch back you just need to repeat the above process but the other way around (e.g. convert the DR database back to a standby and the primary database back to primary).
2. Activating a Standby Database
If the primary database is not available the standby database can be converted into the primary database as follows:
SQL> alter database recover managed standby database cancel;
SQL> alter database activate standby database;
SQL> shutdown immediate
SQL> startup
The original primary database is now obsolete and can be rebuilt as a standby database once it is available again.
3. Opening the Standby Database in Read Only Mode (Active Dataguard)
The standby database can be opened in read only mode for querying and then converted back into a standby database without affecting the primary.
On standby server:
SQL> alter database recover managed standby database cancel;
SQL> alter database open read only;
The standby database is now open and available for querying in read only mode.
To put the standby database back into standby mode:
SQL> shutdown immediate
SQL> startup nomount
SQL> alter database mount standby database;
SQL> alter database recover managed standby database disconnect;