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 : 25-04-2017
ORA-16573

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-29551 : could not convert string to Unicode
  • ora-02276 : default value type incompatible with column type
  • ora-23611 : tablespace "string" has more than one data file
  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • ora-21561 : OID generation failed
  • ora-14116 : partition bound of partition "string" is too long
  • ora-38436 : attribute set used for an Expression set may not be modified.
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-15130 : diskgroup "string" is being dismounted
  • ora-12062 : transaction string received out of sequence from site string
  • ora-03128 : connection is in blocking mode
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-00283 : recovery session canceled due to errors
  • ora-06500 : PL/SQL: storage error
  • ora-06121 : NETTCP: access failure
  • ora-13501 : Cannot drop SYSAUX tablespace
  • ora-08498 : Warning: picture mask 'string' overrides picture mask option 'USAGE IS string' to 'USAGE IS DISPLAY'
  • ora-28234 : key length too short
  • ora-19913 : unable to decrypt backup
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-24908 : invalid recipient presentation attribute
  • ora-19956 : database should have no offline immediate datafiles
  • ora-27152 : attempt to post process failed
  • ora-30931 : Element 'string' cannot contain mixed text
  • ora-15080 : synchronous I/O operation to a disk failed
  • ora-24342 : unable to destroy a mutex
  • ora-10267 : Inhibit KSEDMP for testing
  • ora-19378 : invalid mode
  • ora-26005 : Invalid handle for direct path load
  • ora-30104 : 'string' is not a legal integer for '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.