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 : 28-06-2017

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

  • ora-00361 : cannot remove last log member string for group string
  • ora-31668 : Timeout before worker process string finished initialization.
  • ora-04069 : cannot drop or replace a library with table dependents
  • ora-02165 : invalid option for CREATE DATABASE
  • ora-12496 : cannot change existing level, category, or release numbers
  • ora-12540 : TNS:internal limit restriction exceeded
  • ora-19320 : Host name not specified in HTTP URL
  • ora-07503 : scgcmn: $setimr unexpected return
  • ora-13629 : The task or object string is being used by another operation.
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-00051 : timeout occurred while waiting for a resource
  • ora-14189 : this physical attribute may not be specified for an index subpartition
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-00132 : syntax error or unresolved network name 'string'
  • ora-14079 : illegal option for a partition marked Index Unusable
  • ora-02092 : out of transaction table slots for distributed transaction
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-30338 : illegal dimension hierachy name
  • ora-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-00298 : Missing or invalid attribute value
  • ora-00991 : only MAC privileges may be granted to procedures
  • ora-17504 : ksfddel:Failed to delete file string
  • ora-16531 : unable to post message
  • ora-07620 : smscre: illegal database block size
  • ora-36980 : (XSRELGID02) Variable workspace object must have a numeric data type.
  • ora-31404 : all input parameters are null
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-27060 : could not set close-on-exec bit on file
  • ora-39175 : Encryption password is not needed.
  • ora-29328 : too many datafiles in this tablespace '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.