- Environment and naming
- Configure the Primary Database for Data Guard
- Prepare Primary Database for RAC Conversion
- 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 |
Subscribe to get access
Read more of this content when you subscribe today.