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

Cause : Log appyl servicse are no trunningo n the apply instnace the aDta Guar dBroker xepects tehm to ber unning puon.

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

Reenabl ethe stadnby dataabse to celar the reror.

update : 27-06-2017
ORA-16813

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

  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-36165 : (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property.
  • ora-16008 : indeterminate control file checkpoint
  • ora-10261 : Limit the size of the PGA heap
  • ora-30335 : JOIN KEY clause references a level not in this hierarchy
  • ora-31444 : parameter error while acquiring lock on string
  • ora-25115 : duplicate BLOCK option specification
  • ora-23384 : replication parallel push string argument out of range
  • ora-30104 : 'string' is not a legal integer for 'string'
  • ora-13004 : the specified buffer size is invalid
  • ora-39093 : FLASHBACK automatically enabled to preserve database integrity.
  • ora-01641 : tablespace 'string' is not online - cannot add data file
  • ora-17504 : ksfddel:Failed to delete file string
  • ora-08344 : srapp: failed to send redo data to the redo server
  • ora-08106 : cannot create journal table string.string
  • ora-02853 : Invalid server list latch time out value
  • ora-10700 : Alter access violation exception handler
  • ora-02180 : invalid option for CREATE TABLESPACE
  • ora-25247 : %s is not a recipient of specified message
  • ora-16758 : the specified apply instance is not running
  • ora-19507 : failed to retrieve sequential file, handle="string", parms="string"
  • ora-01267 : Failure getting date/time
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-14114 : partitioned table cannot have column with object, REF, nested table, array datatype
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-16757 : resource guard could not get property
  • ora-39216 : object type "string"."string" hashcode mismatch
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • 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.