ORA-16572: Data Guard configuration file not found

Cause : The Data Guard broker configuration file was either unavailable or did not exist.

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

Verify that the configuration file was successfully created. If the dg_broker_config_file[1|2] parameter was changed, ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.

update : 21-07-2017

ORA-16572 - Data Guard configuration file not found
ORA-16572 - Data Guard configuration file not found

  • ora-12532 : TNS:invalid argument
  • ora-19239 : XP0019 - step expression must return sequence of nodes
  • ora-09876 : TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
  • ora-35021 : (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object.
  • ora-29508 : query derived from USING clause did not select a value of type string
  • ora-24274 : no row exists in the string table for these parameters
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-30448 : internal data of the advisor repository is inconsistent
  • ora-00116 : SERVICE_NAMES name is too long
  • ora-30063 : Internal Event to Test NTP
  • ora-27477 : "string.string" already exists
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-30743 : "string" is not an object view
  • ora-01719 : outer join operator (+) not allowed in operand of OR or IN
  • ora-16083 : LogMiner session has not been created
  • ora-03203 : concurrent update activity makes space analysis impossible
  • ora-14402 : updating partition key column would cause a partition change
  • ora-29823 : object being analyzed is not a table
  • ora-02311 : cannot alter with COMPILE option a valid type with type or table dependents
  • ora-13606 : the specified task parameter element string is out of range for parameter string.
  • ora-19854 : error obtaining connect string from target
  • ora-02456 : The HASH IS column specification must be NUMBER(*,0)
  • ora-26060 : Can not convert type identifier for column string
  • ora-25111 : creation of BITMAP cluster indices is not supported
  • ora-28669 : bitmap index can not be created on an IOT with no mapping table
  • ora-13011 : value is out of range
  • ora-38472 : VARCHAR representation of the data item is too long.
  • ora-16225 : Missing LogMiner session name for Streams
  • ora-31417 : column list contains control column string
  • ora-30349 : specified dimension hierarchy does not exist
  • 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.