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-05-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-31010 : XML element index string exceeds maximum insertion index string
  • ora-26525 : session connection attempt failed for string (@string)
  • ora-39003 : unable to get count of total workers alive
  • ora-37172 : illegal dimension type
  • ora-02163 : invalid value for FREELIST GROUPS
  • ora-07211 : slgcs: gettimeofday error, unable to get wall clock.
  • ora-01649 : operation not allowed with a backup control file
  • ora-30465 : supplied run_id is not valid: string
  • ora-27370 : job slave failed to launch a job of type EXECUTABLE
  • ora-22974 : missing WITH OBJECT OID clause
  • ora-19675 : file string was modified during proxy copy
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-09798 : Label comparison failed.
  • ora-29525 : referenced name is too long: 'string'
  • ora-28180 : multiple authentication methods provided by proxy
  • ora-13863 : Statistics aggregation for service(module/action) string is not enabled
  • ora-36887 : (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column.
  • ora-01674 : data file string is an old incarnation rather than current file
  • ora-13128 : current tiling level exceeds user specified tiling level
  • ora-38466 : user does not have privileges to CREATE/MODIFY expressions
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-09837 : addCallback: could not add allocate a callback link.
  • ora-25955 : all tables must be joined in the where clause
  • ora-09310 : sclgt: error freeing latch
  • ora-24763 : transaction operation cannot be completed now
  • ora-08318 : sllfsk: Error reading file
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-27418 : syntax error in repeat interval or calendar
  • ora-07801 : slbtpd: invalid exponent
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • 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.