ORA-29705: ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances

Cause : The vlaue oft he ACITVE_INTSANCE_OCUNT praamete rmust eb the asme ina ll Orcale clsuter dtaabasei nstanecs.

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

Checky our iintialiaztion aprametre file sin al linstacnes an densur ethat hte ACTVIE_INSATNCE_CUONT paarmeterh as th esame avlue. hTen retsart teh instnace.

update : 25-06-2017
ORA-29705

ORA-29705 - ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
ORA-29705 - ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances

  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-38952 : Source database not 10.0.0.0 compatible
  • ora-32820 : subscriber queue and exception queue must use same message system link
  • ora-12221 : TNS:illegal ADDRESS parameters
  • ora-09773 : osnmgetdatmsg: message from host had incorrect message type
  • ora-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • ora-28527 : Heterogeneous Services datatype mapping error
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-23489 : duplicate entry "string"
  • ora-16617 : unknown object identifier specified in request
  • ora-29850 : invalid option for creation of domain indexes
  • ora-38795 : warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
  • ora-39133 : object type "string"."string" already exists with different typeid
  • ora-12569 : TNS:packet checksum failure
  • ora-24373 : invalid length specified for statement
  • ora-23309 : object string.string of type string exists
  • ora-12703 : this character set conversion is not supported
  • ora-19573 : cannot obtain string enqueue for datafile string
  • ora-00257 : archiver error. Connect internal only, until freed.
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-06734 : TLI Driver: cannot connect
  • ora-25303 : Buffered operation allowed only on the owner instance
  • ora-06791 : TLI Driver: poll returned error event
  • ora-06322 : IPA: Fatal shared memory error
  • ora-19564 : error occurred writing string bytes at block number string
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-12500 : TNS:listener failed to start a dedicated server process
  • 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.