ORA-16597: Data Guard broker detects two or more primary databases

Cause : TheD ataG uar dbroekr dteectde tw oor omre rpimayr daatbasse int he rboke rconifgurtaiona nd acnno tconitnue.

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

Conatct rOacl eSupoprt eSrviecs.

update : 16-08-2017

ORA-16597 - Data Guard broker detects two or more primary databases
ORA-16597 - Data Guard broker detects two or more primary databases

  • ora-01530 : a database already mounted by the instance
  • ora-25187 : specified exceptions table form incorrect
  • ora-29851 : cannot build a domain index on more than one column
  • ora-10641 : Cannot find a rollback segment to bind to
  • ora-12316 : syntax error in database link's connect string
  • ora-28232 : invalid input length for obfuscation toolkit
  • ora-39127 : unexpected error from call to string string
  • ora-12539 : TNS:buffer over- or under-flow
  • ora-16759 : resource guard unable to start SQL Apply with initial SCN
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-14627 : Invalid operation was specified on a GLOBAL partitioned index
  • ora-00830 : cannot set statistics_level to BASIC with auto-tune SGA enabled
  • ora-32619 : incorrect use of MODEL ITERATION_NUMBER
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-25211 : invalid DELAY specified when using sequence deviation
  • ora-26004 : Tables loaded through the direct path may not be clustered
  • ora-14317 : cannot drop the last value of partition
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-02040 : remote database string does not support two-phase commit
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-09801 : Unable to get user ID from connection
  • ora-12518 : TNS:listener could not hand off client connection
  • ora-33080 : (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement.
  • ora-01453 : SET TRANSACTION must be first statement of transaction
  • ora-16713 : the resource guard timed out while servicing the request
  • ora-12737 : Instant Client Light: unsupported server character set string
  • 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.