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 : 23-04-2017

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

  • ora-24904 : invalid callback attribute passed into OCI call
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-19921 : maximum number of string rows exceeded
  • ora-37101 : (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
  • ora-06778 : TLI Driver: error sending ccode
  • ora-06402 : NETCMN: error receiving break message
  • ora-28602 : statement not permitted on tables containing bitmap indexes
  • ora-40284 : model does not exist
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-29925 : cannot execute string
  • ora-08100 : index is not valid - see trace file for diagnostics
  • ora-12985 : tablespace 'string' is read only, cannot drop column
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-14252 : invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
  • ora-01529 : error closing file 'string'
  • ora-13844 : no new SQL profile name or category specified.
  • ora-19124 : fn:one-or-more() called with a sequence containing no items
  • ora-14322 : DEFAULT partition already exists
  • ora-01914 : invalid auditing option for sequence numbers
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-03298 : cannot shrink datafile - file string is under hot backup
  • ora-19802 : cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
  • ora-38862 : FLASHBACK DATABASE in progress
  • ora-27103 : internal error
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-39137 : cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata
  • ora-12731 : invalid collation class in regular expression
  • ora-01987 : client os username is too long
  • 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.