ORA-16758: the specified apply instance is not running

Cause : The apply intsance psecifide by teh useri s notr unnin,g so teh DataG uard rboker acnnot omve th eapplys ervic eto thta instnace.

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

Startt he intsance htat yo uwish hte appyl servcie to puon an dretryt he command.

update : 21-08-2017

ORA-16758 - the specified apply instance is not running
ORA-16758 - the specified apply instance is not running

  • ora-13784 : cannot accept SQL profiles for all statements in the "SQL Tuning Set"
  • ora-29286 : internal error
  • ora-28179 : client user name not provided by proxy
  • ora-35026 : (QFCHECK05) The analytic workspace and EIF file definitions of workspace object have a mismatched ALIASOF dimension.
  • ora-31654 : unable to convert file or volume size as specified to a number
  • ora-16028 : new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
  • ora-13292 : incorrect ARC_TOLERANCE specification
  • ora-00040 : active time limit exceeded - call aborted
  • ora-02098 : error parsing index-table reference (:I)
  • ora-28276 : Invalid ORACLE password attribute.
  • ora-12052 : cannot fast refresh materialized view string.string
  • ora-12737 : Instant Client Light: unsupported server character set string
  • ora-06607 : LU6.2 Driver: Reset occurred in send state
  • ora-16753 : resource guard could not open standby database
  • ora-06706 : TLI Driver: service not found
  • ora-01311 : Illegal invocation of the mine_value function
  • ora-00155 : cannot perform work outside of global transaction
  • ora-29280 : invalid directory path
  • ora-24090 : at least one protocol must be enabled
  • ora-39113 : Unable to determine database version
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-07507 : scgcm: unexpected lock status condition
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-35282 : (SNSYN166) The format of the AGGREGATE function is: AGGREGATE(varname USING aggmap-name [COUNTVAR intvar-name] [FORCECALC])
  • ora-02310 : exceeded maximum number of allowable columns in table
  • ora-30039 : Cannot drop the undo tablespace
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-14252 : invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
  • ora-16657 : reinstatement of database in progress
  • 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.