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 : 26-05-2017

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

  • ora-13374 : SDO_MBR not supported for geodetic data
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-13033 : Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
  • ora-12706 : this CREATE DATABASE character set is not allowed
  • ora-33247 : (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-23342 : invalid parameter column string
  • ora-01226 : file header of log member is inconsistent with other members
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-16514 : the request was not found
  • ora-16650 : command incompatible when Fast-Start Failover is enabled
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-13210 : error inserting data into the index table
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-04933 : initial service identifier is non-zero
  • ora-37104 : (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.
  • ora-27153 : wait operation failed
  • ora-00259 : log string of open instance string (thread string) is the current log, cannot archive
  • ora-29381 : plan/consumer_group string referred to by another plan and cannot be deleted
  • ora-23347 : datatype string for column string table string not supported
  • ora-16791 : unable to check the existence of the standby redo logs
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-13451 : GeoRaster metadata scaling function error
  • ora-38452 : Expression Filter index name may not be longer than 25 characters
  • ora-38029 : object statistics are locked
  • ora-13052 : unsupported geometric type for geometry string.string
  • ora-19957 : database should have no datafiles in unknown state
  • ora-00209 : control file blocksize mismatch, check alert log for more info
  • ora-15068 : maximum number of diskgroups string already mounted
  • ora-39058 : current object skipped: string of type string
  • ora-13363 : no valid ETYPE in the geometry
  • 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.