Oracle Error Message
ORA-16627: operation disallowed since no standby databases would remain to support protection mode
Reason for the Error
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.
Solution
– 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.
