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 : 23-06-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-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-02710 : osnpop: fork failed
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • ora-29909 : label for the ancillary operator is not a literal number
  • ora-36850 : (XSLMGEN20) View token string is not correct
  • ora-32638 : Non unique addressing in MODEL dimensions
  • ora-12987 : cannot combine drop column with other operations
  • ora-13348 : polygon boundary is not closed
  • ora-19018 : Invalid character in XML tag 'string'
  • ora-31221 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd.
  • ora-12200 : TNS:could not allocate memory
  • ora-31608 : specified object of type string not found
  • ora-38488 : attribute set already assigned to the column storing expressions
  • ora-00093 : %s must be between string and string
  • ora-19112 : error raised during evaluation: string
  • ora-06905 : CMX: connect error
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-32313 : REFRESH FAST of "string"."string" unsupported after PMOPs
  • ora-32743 : command cannot be executed on remote instance
  • ora-25311 : %s not supported for non-persistent queue
  • ora-30977 : invalid Value Index option for XML Index
  • ora-02491 : missing required keyword ON or OFF in AUTOEXTEND clause
  • ora-27455 : Only "SYS" is a valid schema for a string.
  • ora-39052 : cannot specify SKIP_CURRENT on initial start of a job.
  • ora-19113 : trace function called during evaluation: string
  • ora-16215 : history metadata inconsistency
  • ora-25285 : Invalid value string for array_mode
  • ora-01514 : error in log specification: no such log
  • ora-06021 : NETASY: connect failed
  • 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.