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 : 22-08-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-13625 : %s is an invalid advisor object type.
  • ora-13122 : invalid topo_geometry specified
  • ora-28556 : authorization insufficient to access table
  • ora-30967 : operation directly on the Path Table is disallowed
  • ora-01673 : data file string has not been identified
  • ora-24185 : transformation string.string does not exist
  • ora-29523 : authorization error for unknown referenced name
  • ora-38728 : Cannot FLASHBACK DATABASE to the future.
  • ora-31666 : Master process string had an unhandled exception.
  • ora-28583 : remote references are not permitted during agent callbacks
  • ora-13864 : Statistics aggregation for service (module/action) string is already enabled
  • ora-01411 : cannot store the length of column in the indicator
  • ora-36639 : (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.
  • ora-34344 : (MXDSS03) Analytic workspace string is not attached.
  • ora-29931 : specified association does not exist
  • ora-13331 : invalid LRS segment
  • ora-06404 : NETCMN: invalid login (connect) string
  • ora-12059 : prebuilt table "string"."string" does not exist
  • ora-01979 : missing or invalid password for role 'string'
  • ora-19688 : control file autobackup format(string) for string does not have %F
  • ora-39165 : Schema string was not found.
  • ora-27411 : empty string is not a valid repeat interval.
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-19044 : character length specified for XMLSerialize is too small.
  • ora-30970 : option not supported for XML Index
  • ora-32033 : unsupported column aliasing
  • ora-27024 : skgfqsbi: sbtinit2 returned error
  • ora-09946 : File name too long for buffer
  • ora-39070 : Unable to open the log file.
  • ora-01323 : Invalid state
  • 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.