How to Setup Data Guard between Non-RAC and RAC Databases

• Environment and naming
• Configure the Primary Database for Data Guard
  1. Enable Archiving
  2. Password File and Parameter
  3. Enable force logging
  4. Configure the Primary Database Initialization Parameters
• Prepare Primary Database for RAC Conversion
  1.  Add additional threads of redo and standby redo logs
  2. Add an undo tablespace for each instance
  3. Run catclust.sql
• Create the Standby Database
• Switchover Production to the new RAC Database

Environment and Naming

A client wants to migrate a mission critical non-RAC database into RAC , and the allowed downtime is less than five minutes. So we recommend to creates data guard of the RAC standby from the non-RAC primary database which can then be used for a role transition.

 The following environment is used as an example to describe the procedure.

Current Non-RAC Primary Database

HOST NAME	primhost
DB_NAME	PRIMDB
DB_UNIQUE_NAME	PRIMDB
SERVICE NAME	SAPSERVICE

RAC Standby Database to be Built

Node1
HOST NAME	stdby1host
DB_NAME	PRIMDB
DB_UNIQUE_NAME	STDBYDB
SERVICE_NAMES	SAPSERVICE
INSTANCE_NAME	STDBYDB1
INSTANCE_NUMBER	1
THREAD	1
UNDO_TABLESPACE	UNDOTBS1

Node2
HOSTNAME	stdby2host
DB_NAME	PRIMDB
DB_UNIQUE_NAME	STDBYDB
SERVICE_NAMES	SAPSERVICE
INSTANCE_NAME	STDBYDB2
INSTANCE_NUMBER	2
THREAD	2
UNDO_TABLESPACE	UNDOTBS2