The following is the ORA-16627 error message, you can learn the cause and solution of the Oracle database error.


ORA-16627 no standby databases support overall protection mode

Cause: This status is returned in the following situations:

  • The Broker rejects an attempt to change the configuration’s overall protection mode since it could not find any online, managed standby databases that support the proposed protection mode.
  • The Broker rejects an attempt to enable the configuration if it determines that there are no online managed standby databases that support the overall protection mode.
  • The Broker rejects an attempt to disable or delete a site or database resource, that if disabled or deleted, would result in no standby databases that support the configuration’s overall protection mode.
  • The Broker rejects an attempt to set the configuration offline if doing so would violate the configuration’s overall protection mode.
  • The Broker rejects an attempt to set a standby site or database offline if doing so would violate the configuration’s overall protection mode.
  • The Broker rejects a switchover attempt if doing so would violate the configuration’s overall protection mode.
  • The Broker returns this error during a health check.

Solution:

  • If changing the overall protection mode, then 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 configuration 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 configuration property setting that supports the overall protection mode.
  • For the state change failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If setting the configuration OFFLINE, you may have to downgrade the protection mode setting to maximum performance beforehand.
  • For switchover failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If your configuration contains a primary and a single standby, then ensure that the LogXptMode configuration property established for the primary site supports the overall protection mode. After the switchover the old primary will become the standby and its LogXptMode configuration property setting must support the overall protection mode.
  • For health check error, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.
Case:

Please wait for the update…