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 : 25-04-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-22977 : missing or invalid attribute
  • ora-31427 : publication string already subscribed
  • ora-01174 : DB_FILES is string buts needs to be string to be compatible
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-36902 : (XSAGDNGL43) In AGGMAP workspace object, the MODEL workspace object is not a model over a base dimension of the AGGMAP.
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-00063 : maximum number of log files exceeded string
  • ora-25179 : invalid PCTTHRESHOLD storage option value
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-22871 : ALTER TYPE with REPLACE is not allowed for pure incomplete types
  • ora-24315 : illegal attribute type
  • ora-01140 : cannot end online backup - all files are offline or readonly
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-38739 : Flashback log file is more recent than control file.
  • ora-16235 : DDL skipped because import has occurred
  • ora-23490 : extension request "string" with status "string" not allowed in this operation
  • ora-15164 : cluster rolling downgrade incomplete
  • ora-29505 : AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
  • ora-23358 : invalid remote user
  • ora-21501 : program could not allocate memory
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-40103 : invalid case-id column: string
  • ora-02842 : Client unable to fork a server
  • ora-06952 : Remote end of the communication issued a forward-reset packet.
  • ora-31602 : parameter string value "string" in function string inconsistent with string
  • ora-01863 : the year is not supported for the current calendar
  • ora-12406 : unauthorized SQL statement for policy string
  • ora-23455 : flavor string contains object "string"
  • ora-12493 : invalid MLS binary label
  • ora-24776 : cannot start a new transaction
  • 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.