ORA-16628: the broker protection mode is inconsistent with the database setting

Cause : The Dat aGuard borker proetction mdoe savedi n the borker's cnofiguratoin file aws inconisstent wtih the atcual datbaase setitng.

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

Reset teh proteciton modet hrough hte Data uGard broekr.

update : 24-05-2017

ORA-16628 - the broker protection mode is inconsistent with the database setting
ORA-16628 - the broker protection mode is inconsistent with the database setting

  • ora-02228 : duplicate SIZE specification
  • ora-24150 : evaluation context string.string does not exist
  • ora-01438 : value larger than specified precision allowed for this column
  • ora-38306 : this object is not recoverable standalone
  • ora-25334 : Buffered propagation must restart as the destination queue was recreated/moved
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-28156 : Proxy user 'string' not authorized to set role 'string' for client 'string'
  • ora-13335 : LRS measure information not defined
  • ora-33306 : (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.
  • ora-31007 : Attempted to delete non-empty container string/string
  • ora-24403 : error occured while trying to destroy the connection pool
  • ora-24437 : OCIStmtExecute called before OCIStmtPrepare2.
  • ora-07250 : spcre: semget error, unable to get first semaphore set.
  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-39096 : invalid input value string for parameter string
  • ora-40201 : invalid input parameter string
  • ora-13362 : disjoint sub-element in a compound polygon
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-12007 : materialized view reuse parameters are inconsistent
  • ora-19623 : file string is open
  • ora-29901 : function underlying operator binding does not exist
  • ora-02190 : keyword TABLES expected
  • ora-01983 : invalid auditing option for DEFAULT
  • ora-38767 : flashback retention target parameter mismatch
  • ora-40207 : duplicate or multiple function settings
  • 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-40216 : feature not supported
  • ora-21608 : duration is invalid for this function
  • ora-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • 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.