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 : 29-04-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-35024 : (QFCHECK04) The analytic workspace and EIF file definitions of workspace object have mismatched time dimension attributes.
  • ora-23337 : priority or value not in priority group string
  • ora-27460 : cannot execute disabled job "string.string"
  • ora-38485 : invalid object type for the user-defined function
  • ora-01645 : previous attempt to make read write is half complete
  • ora-12353 : secondary stored object cannot reference remote object
  • ora-07200 : slsid: oracle_sid not set.
  • ora-13827 : null or zero length attribute specified in SQL profile collection
  • ora-13631 : The task string contains no execution results.
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-27421 : usage of string not supported in a calendar definition
  • ora-01520 : number of data files to add (string) exceeds limit of string
  • ora-03127 : no new operations allowed until the active operation ends
  • ora-16578 : failed to read Data Guard configuration file
  • ora-06121 : NETTCP: access failure
  • ora-16740 : redo transport service for standby database "string" incorrectly set to ALTERNATE
  • ora-26680 : object type not supported
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-02264 : name already used by an existing constraint
  • ora-38954 : Cross platform transport is not supported between source platform identifier string and target platform identifier string
  • ora-13798 : Parameter string cannot be NULL.
  • ora-39081 : failed to unsubscribe agent string from queue "string"
  • ora-14319 : DEFAULT cannot be specified with other values
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-19688 : control file autobackup format(string) for string does not have %F
  • ora-30978 : The XML Index is not locally partitioned.
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-21703 : cannot flush an object that is not modified
  • ora-31526 : could not find source table string.string for CDC change table string.string
  • 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.