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-04-2017
ORA-16628

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-25126 : Invalid name specified for BUFFER_POOL
  • ora-14169 : invalid ALTER TABLE MODIFY SUBPARTITION option
  • ora-01495 : specified chain row table not found
  • ora-02457 : The HASH IS option must specify a valid column
  • ora-16701 : generic resource guard request failed
  • ora-14162 : subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-00369 : Current log of thread string not useable and other log being cleared
  • ora-30690 : timeout occurred while registering a TCP/IP connection for data traffic detection
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-00473 : ARCH process terminated with error
  • ora-24439 : success with PLSQL compilation warning
  • ora-27021 : sequential file handle must be specified
  • ora-24307 : invalid length for piece
  • ora-31115 : XDB configuration error: string
  • ora-19921 : maximum number of string rows exceeded
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-33247 : (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-30077 : illegal casting between specified datetime types
  • ora-28267 : Invalid NameSpace Value
  • ora-10900 : extent manager fault insertion event #string
  • ora-09766 : osnmop: buffer allocation failure.
  • ora-08267 : destroy_ora_addr: cannot close nameserver
  • ora-31221 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd.
  • ora-38856 : cannot mark instance string (redo thread string) as enabled
  • ora-31459 : system triggers for DBMS_CDC_PUBLISH package are not installed
  • ora-31418 : source schema string does not exist
  • ora-16005 : database requires recovery
  • ora-30961 : internal SQL statement is too long
  • ora-01943 : IDENTIFIED BY already specified
  • ora-25255 : incorrect subscription string 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.