ORA-16627: operation disallowed since no standby databases 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 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.

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 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.

ORA-16628
Custom Search


More Oracle errors
ORA-06435ssaio: write error, unable to write requested block to database file.
RMAN-00701SCRIPT requires that CATALOG be specified on the command line
TNS-12583TNS:no reader
ORA-16820fast-start failover observer is no longer observing this database
ORA-27477"string.string" already exists
ORA-30927Unable to complete execution due to failure in temporary table transformation
PCB-00108Unable to open list file "string"
ORA-00362member is required to form a valid logfile in group string
ORA-36636(XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
RMAN-10027could not locate network layer context
SQL*Loader-00949incorrect datafile string specified for table string subpartition string
ORA-28368cannot auto-create wallet
CLST-02108missing required parameter -q with path to the voting device
ORA-16050destination exceeded specified quota size
ORA-12400invalid argument to facility error handling
PCC-02389Arrays not allowed as input bind variables in SELECT list
ORA-00710new tablespace name is the same as the old tablespace name
ORA-07417sfareq: One or more database writers not active.
ORA-01145offline immediate disallowed unless media recovery enabled
ORA-39219directory object name is too long




TOP 20 Oracle errors
ORA-12504TNS:listener was not given the SERVICE_NAME in CONNECT_DATA
RMAN-20079full resync from primary database is not done
ORA-14411The DDL cannot be run concurrently with other DDLs
ORA-14760ADD PARTITION is not permitted on Interval partitioned objects
ORA-10877error signaled in parallel recovery slave string
ORA-32701Hang detected
ORA-00838Specified value of MEMORY_TARGET is too small, needs to be at least stringM
ORA-16957SQL Analyze time limit interrupt
ORA-16664unable to receive the result from a database
ORA-16766Redo Apply is stopped
RMAN-08132WARNING: cannot update recovery area reclaimable file list
ORA-00000normal, successful completion
ORA-16665timeout waiting for the result from a database
ORA-00837Specified value of MEMORY_TARGET greater than MEMORY_MAX_TARGET
RMAN-08137WARNING: archived log not deleted as it is still needed
DIA-48122error with opening the ADR block file [string] [string]
ORA-47988password should contain at least one numeric and one alphabetic character
IMP-00057Warning: Dump file may not contain data of all partitions of this table
ORA-55508Invalid input to Flashback Transaction Backout
ORA-00001unique constraint (string.string) violated




Your own TOP 20 Oracle errors
ORA-16627operation disallowed since no standby databases would remain to support protection mode