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 : 20-08-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-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-28022 : cannot grant external roles to global user or role
  • ora-29548 : Java system class reported: string
  • ora-24392 : no connection pool to associate server handle
  • ora-28365 : wallet is not open
  • ora-16238 : attempt to use version 9 log
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-16794 : database guard is on for primary database
  • ora-12647 : Authentication required
  • ora-22281 : cannot perform operation with an updated locator
  • ora-28547 : connection to server failed, probable Oracle Net admin error
  • ora-02162 : invalid value for MAXDATAFILES
  • ora-00404 : Convert file not found: 'string'
  • ora-14321 : cannot add/drop values to DEFAULT partition
  • ora-19776 : PROXY restore to ASM diskgroup "string" is not supported.
  • ora-24237 : object id argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-23387 : replication parallel push dequeue error
  • ora-19624 : operation failed, retry possible
  • ora-24265 : Insufficient privileges for SQL profile operation
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-27505 : IPC error destroying a port
  • ora-07255 : spini: cannot set up signal handler.
  • ora-01312 : Specified table/column does not exist
  • ora-29802 : missing CONTEXT keyword
  • ora-24062 : Subscriber table string inconsistent with queue table string
  • ora-40220 : maximum number of attributes exceeded
  • ora-25964 : column type incompatible with join column type
  • ora-31514 : change set string disabled due to capture error
  • 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.