.ora-code.com

Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
ORA-16627
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.

User Posts


No registration required.
Post Topic:
Oracle Database Server Error Codes
ORA-00020   ORA-00054   ORA-00119   ORA-00279   ORA-00381   ORA-00439   ORA-00600   ORA-00604   ORA-00904   ORA-00907   ORA-00911   ORA-00922   ORA-00923   ORA-00936   ORA-00942   ORA-01000   ORA-01017   ORA-01031   ORA-01033   ORA-01034   ORA-01078   ORA-01092   ORA-01113   ORA-01122   ORA-01161   ORA-01422   ORA-01501   ORA-01555   ORA-01562   ORA-01578   ORA-01650   ORA-01652   ORA-01658   ORA-01722   ORA-01756   ORA-01843   ORA-01925   ORA-01940   ORA-02019   ORA-02097   ORA-02143   ORA-03113   ORA-04030   ORA-04031   ORA-04068   ORA-06502   ORA-06512   ORA-06531   ORA-06550   ORA-07445   ORA-12154   ORA-12203   ORA-12500   ORA-12535   ORA-12540   ORA-12545   ORA-12560   ORA-12599   ORA-12638   ORA-12709   ORA-12838   ORA-12913   ORA-16038   ORA-20000   ORA-24324   ORA-27125   ORA-28575   ORA-28576   ORA-29283   ORA-29540   ORA-32004