ORA-16571: Data Guard configuration file creation failure

Cause : The Data Guard broker was unable to create the configuration file on permanent storage.

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

Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters and retry.

update : 18-08-2017

ORA-16571 - Data Guard configuration file creation failure
ORA-16571 - Data Guard configuration file creation failure

  • ora-24762 : server failed due to unspecified error
  • ora-12197 : TNS:keyword-value resolution error
  • ora-02060 : select for update specified a join of distributed tables
  • ora-31410 : change set string is not an existing change set
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-12452 : label tag string already exists
  • ora-19658 : cannot inspect string - file is from different resetlogs
  • ora-26525 : session connection attempt failed for string (@string)
  • ora-02793 : Close of asynchronous I/O failed.
  • ora-30063 : Internal Event to Test NTP
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-30012 : undo tablespace 'string' does not exist or of wrong type
  • ora-30975 : invalid Order Key Index option for XML Index
  • ora-39026 : master table is inconsistent on validation string
  • ora-06913 : CMX: error during redirection of connection
  • ora-02846 : Unkillable server
  • ora-09365 : Windows 3.1 Two-Task driver unable to destroy hidden window
  • ora-31504 : cannot alter or drop predefined change source
  • ora-19752 : block change tracking is already enabled
  • ora-01607 : cannot add logfile to the specified instance
  • ora-28366 : invalid database encryption operation
  • ora-12236 : TNS:protocol support not loaded
  • ora-03242 : Tablespace migration retried 500 times
  • ora-26078 : file "string" is not part of database being loaded
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-02831 : Segment deallocation failed - empty segment list
  • ora-06318 : IPA: Local maximum number of connections exceeded
  • ora-29345 : cannot plug a tablespace into a database using an incompatible character set
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • 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.