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. are no online, enabled standby databases that support the overall protection mode. deleted, would result in no remaining standby databases that can support the configuration s overall protection mode. violate the configuration s overall protection mode. violate the configuration s overall protection mode. configuration s overall protection mode.
Action: - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode. configuration property setting that supports the current overall protection mode. has a LogXptMode configuration property setting that supports the overall protection mode. 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. 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.
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. are no online, enabled standby databases that support the overall protection mode. deleted, would result in no remaining standby databases that can support the configuration s overall protection mode. violate the configuration s overall protection mode. violate the configuration s overall protection mode. configuration s overall protection mode.
Action: - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode. configuration property setting that supports the current overall protection mode. has a LogXptMode configuration property setting that supports the overall protection mode. 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. 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.
No comments:
Post a Comment