ORA-16627: operation disallowed since no standby databases would remain to support 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, enabled standby databases that support the proposed protection mode.
- The broker rejects an attempt to enable the configuration if it determines there are no online, enabled standby databases that support the overall protection mode.
- The broker rejects an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that can 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 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.
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 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 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 database and a single standby database, ensure that the LogXptMode configuration property established for the primary database supports the overall protection mode. After the switchover, the old primary database will become the standby database 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.
Back to previous menu
https://support.oracle.com/
http://www.oracle.com/