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-05-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-07390 : sftopn: translate error, unable to translate file name.
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-30061 : Internal Event for Savepoint Tracing
  • ora-38779 : cannot create restore point - too many restore points.
  • ora-01323 : Invalid state
  • ora-21779 : duration not active
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • ora-25293 : Lob attributes must be null for buffered operations
  • ora-32140 : cannot peform this operation on stream
  • ora-13780 : SQL statement does not exist.
  • ora-00101 : invalid specification for system parameter DISPATCHERS
  • ora-30121 : 'string' is not an allowable value for 'string'
  • ora-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • ora-01572 : rollback segment 'string' cannot be brought online, string extents exceeded
  • ora-32053 : operation not supported
  • ora-14041 : partition bound may not be specified for resulting partitions
  • ora-24435 : Invalid Service Context specified.
  • ora-16724 : the intended state for the database has been set to OFFLINE
  • ora-24309 : already connected to a server
  • ora-36668 : (XSDPART06) string is not a legal RANGE partition.
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • ora-14031 : partitioning column may not be of type LONG or LONG RAW
  • ora-02141 : invalid OFFLINE option
  • ora-10571 : Test recovery canceled
  • ora-23498 : repgroups specified must have the same masters
  • ora-13798 : Parameter string cannot be NULL.
  • ora-25197 : an overflow segment already exists for the indexed-organized table
  • ora-06770 : TLI Driver: error sending version
  • ora-00053 : maximum number of enqueues exceeded
  • 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.