ORA-16775: target standby database in broker operation has potential data loss

Cause : The target standby database in the broker operation did not have all the redo logs from the primary database. The switchover or protection mode upgrade to maximum protection could not be performed.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Query the SendQEntries monitorable property on the primary database to see which redo logs are missing. Confirm that the redo transport service on the primary database is functioning correctly by checking its status using the StatusReport monitorable property. Perform log switches on the primary database in order to activate the redo log gap fetching mechanism. Once all redo logs are available on the target standby database, reissue the broker command.

update : 23-06-2017

ORA-16775 - target standby database in broker operation has potential data loss
ORA-16775 - target standby database in broker operation has potential data loss

  • ora-24309 : already connected to a server
  • ora-22874 : attribute "string" is not part of the type "string"
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-31099 : XDB Security Internal Error
  • ora-01208 : data file is an old version - not accessing current version
  • ora-00337 : log file 'string' does not exist and no size specified
  • ora-29351 : can not transport system, sysaux, or temporary tablespace 'string'
  • ora-13047 : unable to determine ordinate count from table _SDOLAYER
  • ora-02264 : name already used by an existing constraint
  • ora-14509 : specified VALIDATE INTO table form incorrect
  • ora-39727 : COMPATIBLE must be set to or higher
  • ora-01079 : ORACLE database was not properly created, operation aborted
  • ora-15175 : cannot create alias for diskgroup metadata file 'string'
  • ora-14619 : resulting List subpartition(s) must contain at least 1 value
  • ora-31457 : maximum length of description field exceeded
  • ora-06120 : NETTCP: network driver not loaded
  • ora-31417 : column list contains control column string
  • ora-12731 : invalid collation class in regular expression
  • ora-06567 : invalid number of values specified
  • ora-16647 : could not start more than one observer
  • ora-28104 : input value for string is not valid
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-01987 : client os username is too long
  • ora-13119 : invalid edge_id [string]
  • ora-14627 : Invalid operation was specified on a GLOBAL partitioned index
  • ora-10572 : Test recovery canceled due to errors
  • ora-10841 : Default un-inintialized charact set form to SQLCS_IMPLICIT
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-39701 : database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
  • ora-24038 : RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.