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-07-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-02471 : SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
  • ora-28660 : Partitioned Index-Organized table may not be MOVEd as a whole
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-30048 : Internal event for IMU auto-tuning
  • ora-06573 : Function string modifies package state, cannot be used here
  • ora-09812 : Unable to get user clearance from connection
  • ora-28556 : authorization insufficient to access table
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-06317 : IPA: Local maximum number of users exceeded
  • ora-23453 : requested operation is not supported on top flavor
  • ora-22279 : cannot perform operation with LOB buffering enabled
  • ora-09708 : soacon: failed to bind socket to port.
  • ora-25197 : an overflow segment already exists for the indexed-organized table
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-24316 : illegal handle type
  • ora-30199 : reserved for future use
  • ora-16046 : Archive log destination failed due to failed dependent destination
  • ora-27373 : unknown or illegal event source queue
  • ora-15194 : Internal ASM-DB interaction testing event number 15194
  • ora-16508 : channel handle not initialized
  • ora-16253 : Logical Standby cannot start due to incomplete terminal apply
  • ora-37069 : You may not execute a parallel OLAP operation against the EXPRESS AW.
  • ora-13139 : could not obtain column definition for string
  • ora-09363 : Windows 3.1 Two-Task driver invalid context area
  • ora-28100 : policy function schema string is invalid
  • ora-40321 : invalid bin number, is zero or negative value
  • ora-31100 : XDB Locking Internal Error
  • ora-28591 : agent control utility: unable to access parameter file
  • ora-32808 : message system link string does not exist
  • ora-06435 : ssaio: write error, unable to write requested block to database file.
  • 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.