ORA-16627: operation disallowed since no member would remain to support

aws-senior.com

www.aws-senior.com
Visite out website www.aws-senior.com
http://www.aws-senior.com
www.aws-senior.com

ORA-16627: operation disallowed since no member would remain to support

ORA-16627: operation disallowed since no member 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 members that supported the proposed protection mode, or could not find any enabled members that were synchronized. – The broker rejected an attempt to enable the configuration if it determined that there were no enabled members that supported the overall protection mode. – The broker rejected an attempt to disable or remove a member that, if disabled or deleted, would result in no remaining member 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 members supported the overall protection mode.

Action: – If changing the overall protection mode, confirm that at least one member satisfies the new protection mode and is synchronized with the primary database. – For enable failures, confirm that at least one member receives redo data in a mode that supports the current overall protection mode. – For delete and disable failures, confirm that at least one other member receives redo data in a mode that suppports the 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 member receives redo data in synchronous mode. 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 a health check error, confirm that at least one member receives redo data in a mode that supports the current overall protection mode.