ORA-16573: attempt to change configuration file for an enabled broker configuration

Cause : The Data Guard broker configuration file parameter was currently in use because broker management of the configuration was enabled. The attempt to alter that parameter was rejected.

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

Disable the configuration and shut down the Data Guard broker before changing this value. Be sure to rename the configuration file at the OS level to match the new value before reenabling broker management of the configuration.

update : 24-06-2017

ORA-16573 - attempt to change configuration file for an enabled broker configuration
ORA-16573 - attempt to change configuration file for an enabled broker configuration

  • ora-06923 : CMX: illegal break condition
  • ora-19561 : %s requires a DISK channel
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-32306 : updatable materialized views with user-defined types must use SELECT *
  • ora-29397 : cannot grant/revoke switch privilege for string
  • ora-31433 : subscriber view does not exist
  • ora-29320 : datafile header error
  • ora-13903 : Invalid combination of string threshold value and operator.
  • ora-12841 : Cannot alter the session parallel DML state within a transaction
  • ora-04075 : invalid trigger action
  • ora-06405 : NETCMN: reset protocol error
  • ora-10570 : Test recovery complete
  • ora-28535 : invalid Heterogeneous Services context
  • ora-15201 : disk string contains a valid RDBMS file
  • ora-16811 : apply instance not recorded by the Data Guard broker
  • ora-29399 : user string does not have privilege to switch to consumer group string
  • ora-13260 : layer table string does not exist
  • ora-02280 : duplicate or conflicting CYCLE/NOCYCLE specifications
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-19103 : VALUE keyword keyword
  • ora-02151 : invalid tablespace name: string
  • ora-12987 : cannot combine drop column with other operations
  • ora-40254 : priors cannot be specified for one-class models
  • ora-24159 : invalid variable definiton
  • ora-27375 : valid agent name must be specified for secure queues
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-23498 : repgroups specified must have the same masters
  • ora-19117 : invalid redefinition of predefined namespace prefix 'string'
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-16757 : resource guard could not get property
  • 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.