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 : 25-04-2017
ORA-16775

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-00704 : bootstrap process failure
  • ora-14113 : partitioned table cannot have column with LOB datatype
  • ora-08318 : sllfsk: Error reading file
  • ora-01253 : cannot start online backup - file string in recovery manager backup
  • ora-39700 : database must be opened with UPGRADE option
  • ora-07493 : scgrcl: lock manager error.
  • ora-01487 : packed decimal number too large for supplied buffer
  • ora-02731 : osnrnf: malloc of buffer failed
  • ora-31628 : error getting worker process exception
  • ora-22970 : name does not correspond to an object view
  • ora-12843 : pdml lock not held properly on the table
  • ora-15041 : diskgroup space exhausted
  • ora-19595 : archivelog string already included in backup conversation
  • ora-31417 : column list contains control column string
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-14152 : invalid number of partitions specified in PARTITIONS clause
  • ora-22346 : Type has cyclical dependency. Should use CASCADE option
  • ora-23379 : connection qualifier "string" is too long
  • ora-16953 : Type of SQL statement not supported.
  • ora-31617 : unable to open dump file "string" for write
  • ora-13702 : Snapshot IDs specified by the range [string, string] are equal.
  • ora-16002 : database already open for read-write access by another instance
  • ora-13040 : failed to subdivide tile
  • ora-19222 : XP0002 - XQuery dynamic context component string not initialized
  • ora-22055 : unknown sign flag value [string]
  • ora-00123 : idle public server terminating
  • ora-00224 : control file resize attempted with illegal record type (string)
  • ora-12219 : TNS:missing community name from address in ADDRESS_LIST
  • ora-02158 : invalid CREATE INDEX option
  • ora-24047 : invalid agent name string, agent name should be of the form NAME
  • 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.