ORA-16811: apply instance not recorded by the Data Guard broker

Cause : The rbokerh as nto regsitere dan apply isntanc efor astanbdy daatbase.

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

Reenbale teh stadnby dtaabas eto celar teh errro.

update : 26-04-2017
ORA-16811

ORA-16811 - apply instance not recorded by the Data Guard broker
ORA-16811 - apply instance not recorded by the Data Guard broker

  • ora-29251 : Index1 is greater than Index2 in call to dbms_sql.bind_array
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-13459 : GeoRaster metadata SRS error
  • ora-28654 : table and partition not overflow compatible
  • ora-07657 : slsprom:$ASSIGN failure
  • ora-09313 : slsprom: error prompting user
  • ora-01875 : time zone minute must be between -59 and 59
  • ora-31502 : invalid number supplied for supplemental_processes
  • ora-02706 : osnshs: host name too long
  • ora-00313 : open failed for members of log group string of thread string
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-32312 : cannot refresh a secondary materialized view "string"."string"
  • ora-23328 : mview base table "string"."string" differs from master table "string"."string"
  • ora-22933 : cannot change object with type or table dependents
  • ora-01157 : cannot identify/lock data file string - see DBWR trace file
  • ora-24005 : must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
  • ora-02420 : missing schema authorization clause
  • ora-25102 : PARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-02276 : default value type incompatible with column type
  • ora-00448 : normal completion of background process
  • ora-32028 : Syslog facility or level not recognized
  • ora-27376 : event condition cannot be NULL
  • ora-01107 : database must be mounted for media recovery
  • ora-02073 : sequence numbers not supported in remote updates
  • ora-00392 : log string of thread string is being cleared, operation not allowed
  • ora-15123 : ASM file name 'string' contains an invalid incarnation number
  • ora-22928 : invalid privilege on directories
  • ora-16233 : The table string.string is unsupported now
  • ora-32806 : value for string is too long, maximum length is string
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • 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.