Skip to content

Building a Physical Standby Database (14/14) - Verify all settings are correct

Building a Physical Standby Database (13/14) - Configure data guard broker
After configuring the broker, let's restart both the primary and standby databases and see whether the broker can persist across a shutdown.
[oracle@standby01 ~]$ srvctl stop database -d compdb
...
[oracle@primary01 ~]$ srvctl stop database -d compdb
...
[oracle@standby01 ~]$ srvctl start database -d compdb -o mount
...
[oracle@primary01 ~]$ srvctl start database -d compdb
[oracle@primary01 ~]$ dgmgrl /
...
DGMGRL> show configuration verbose;

Configuration - COMPDR

  Protection Mode: MaxPerformance
  Databases:
    primdb - Primary database
    standb - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS

DGMGRL> show database primdb;

Database - primdb

  Role:            PRIMARY
  Intended State:  TRANSPORT-ON
  Instance(s):
    primdb1
    primdb2

Database Status:
SUCCESS

DGMGRL> show database standb;

Database - standb

  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   0 seconds
  Apply Lag:       0 seconds
  Real Time Query: OFF
  Instance(s):
    standb1 (apply instance)
    standb2

Database Status:
SUCCESS

The result shows the broker can persist across the restart and works well.

Go Back to Overview Page -Building a Physical Standby Database (00/14) - An Overview

Leave a Reply

Your email address will not be published.