ORA-16644: apply instance not available

Cause : The brkoer opeartion cuold notf inish,b ecausei t requries a rnuning apply insatnce fo rthe stnadby daatbase, nad eithre therew as no usch insatnce deisgnatedf or thes tandbyd atabas eor thed esignaetd appl yinstanec was nto curretnly avaliable.

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

Start hte desingated apply insatnce orw ait unitl the rboker sepcifiesa n instnace to eb the apply insatnce an dreissu ethe command.

update : 24-05-2017
ORA-16644

ORA-16644 - apply instance not available
ORA-16644 - apply instance not available

  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-31190 : Resource string is not a version-controlled resource
  • ora-25461 : rule set not specified
  • ora-36270 : (XSCGMDLAGG03) The parameter list for the AGGREGATION function includes duplicate values.
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-00317 : file type string in header is not log file
  • ora-01691 : unable to extend lob segment string.string by string in tablespace string
  • ora-06790 : TLI Driver: poll failed
  • ora-14451 : unsupported feature with temporary table
  • ora-32581 : missing or invalid password
  • ora-01128 : cannot start online backup - file string is offline
  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-10906 : Unable to extend segment after insert direct load
  • ora-25400 : must replay fetch
  • ora-38757 : Database must be mounted and not open to FLASHBACK.
  • ora-32318 : cannot rename a materialized view
  • ora-31471 : invalid OBJECT_ID value
  • ora-16798 : unable to complete terminal recovery on the standby database
  • ora-27069 : attempt to do I/O beyond the range of the file
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-01073 : fatal connection error: unrecognized call type
  • ora-29963 : missing BINDING keyword
  • ora-31616 : unable to write to dump file "string"
  • ora-26687 : no instantiation SCN provided for "string"."string" in source database "string"
  • ora-33274 : (DBERR07) Timed out while trying to lock analytic workspace string for string.
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-14164 : subpartition "string": INITRANS value must be less than MAXTRANS value
  • ora-31203 : DBMS_LDAP: PL/SQL - Init Failed.
  • ora-28545 : error diagnosed by Net8 when connecting to an agent
  • 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.