What can you conclude based on this error?

B

[oracle@dghost ~]$ oerr ora 16627
16627, 0000, “operation disallowed since no standby databases would remain to support protection mode”
// *Cause: This status was returned because of one of the following:
// – The broker rejected an attempt to change the overall
// configuration protection mode since it could not find any
// enabled standby databases that supported the proposed protection
// mode.
// – The broker rejected an attempt to enable the configuration
// if it determined that there were no enabled standby databases
// that supported the overall protection mode.
// – The broker rejected an attempt to disable or remove a database
// that, if disabled or deleted, would result in no remaining
// standby databases that could support the overall configuration
// protection mode.
// – The broker rejected an attempt to switchover if doing so would
// violate the overall configuration protection mode.
// – Performing automatic health check if the broker determined that
// no standby datbases supported the overall protection mode.
// *Action: – If changing the overall protection mode, confirm that at least
// one standby database satisfies the new protection mode.
// – For enable failures, confirm that at least one standby database
// has a LogXptMode configurable property setting that supports
// the current overall protection mode.
// – For delete and disable failures, confirm that at least one
// other standby database has a LogXptMode configurable property
// setting that supports the overall protection mode.
// – For switchover failures that occur when the configuration
// is operating in maximum protection or maximum availability
// mode, confirm that at least one other standby database has its
// LogXptMode configurable property set to the value “SYNC”.
// If the configuration contains a primary database and a single
// standby database and is operating in either maximum protection
// or maximum availability mode, ensure that the LogXptMode
// configurable property of the primary database is set to the
// value “SYNC”. Since the old primary database will become the
// standby database after switchover completes, its LogXptMode
// configurable property setting must support the configuration
// protection mode.
// – For health check error, confirm that at least one standby
// database has a LogXptMode configurable property setting
// that supports the current overall protection mode.

DGMGRL> show configuration;

Configuration – Animals

Protection Mode: MaxPerformance
Members:
dogs – Primary database
cats – Snapshot standby database
sheep – Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 26 seconds ago)

DGMGRL> edit configuration set protection mode as maxprotection;
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode

Failed.

DGMGRL> edit database sheep set property logxptmode=’SYNC’;
Property “logxptmode” updated

DGMGRL> show configuration;

Configuration – Animals

Protection Mode: MaxPerformance
Members:
dogs – Primary database
sheep – Physical standby database
cats – Snapshot standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 33 seconds ago)

DGMGRL> edit configuration set protection mode as maxprotection;
Operation requires shut down of instance “dogs” on database “dogs”
Shutting down instance “dogs”…
Database closed.
Database dismounted.
ORACLE instance shut down.
Operation requires start up of instance “dogs” on database “dogs”
Starting instance “dogs”…
ORACLE instance started.
Database mounted.
Database opened.

DGMGRL> show configuration;

Configuration – Animals

Protection Mode: MaxProtection
Members:
dogs – Primary database
sheep – Physical standby database
cats – Snapshot standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 60 seconds ago)