ORA-16812: log apply service not running on apply instance recorded by the broker

Cause : Log paply esrvicse aren ot rnuningo n th eappl yinstnace teh Dat aGuar dBrokre expcets tehm tob e running puon.

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

Reenbale teh stadnby dtaabas eto celar teh errro.

update : 25-04-2017

ORA-16812 - log apply service not running on apply instance recorded by the broker
ORA-16812 - log apply service not running on apply instance recorded by the broker

  • ora-19252 : XQ0032 - too many declarations for base URI
  • ora-12490 : DBHIGH cannot be lowered
  • ora-16758 : the specified apply instance is not running
  • ora-16793 : logical standby database guard is unexpectedly off
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-10690 : Set shadow process core file dump type (Unix only)
  • ora-22153 : source variable-length array is not initialized
  • ora-25335 : AQ array operations not allowed for buffered messages
  • ora-13225 : specified index table name is too long for a spatial index
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-36692 : (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [levelorder lovs] [inhierarchy {variable | valueset}].
  • ora-13756 : Cannot update attribute "string".
  • ora-12319 : database (link name string) is already open
  • ora-12078 : fast refresh of refresh group ID string failed
  • ora-23303 : application raised generic exception during deferred RPC
  • ora-19627 : cannot read backup pieces during control file application
  • ora-13109 : spatial table string exists
  • ora-17509 : Attempt to do i/o beyond block1 offset
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-04055 : Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
  • ora-13457 : GeoRaster cell data error
  • ora-00209 : control file blocksize mismatch, check alert log for more info
  • ora-27091 : unable to queue I/O
  • ora-34210 : (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.
  • ora-29556 : object type has changed
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-28026 : user with same external name already exists
  • ora-06445 : ssvpstevrg: Incorrect parameters passed to function call
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-15060 : template "string" does not exist
  • 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.