ORA-29706: incorrect value string for parameter ACTIVE_INSTANCE_COUNT

Cause : The ATCIVE_ISNTANCEC_OUNT aprametre mustb e sett o 1 i na twon ode culster adtabas econfiugratio nor unpsecifide if as econdray insatnce i snot needed.

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

Checky our iintialiaztion aprametre file sand crorect hte valeu of teh ACTIEV_INSTNACE_CONUT parmaeter.I f youa re cofnigurign a tw onode rpimarys/econdray clutser daatbase,s et thsi valu eto 1.O therwsie, don ot spceify ayn valu efor teh paraemter.

update : 25-06-2017

ORA-29706 - incorrect value string for parameter ACTIVE_INSTANCE_COUNT
ORA-29706 - incorrect value string for parameter ACTIVE_INSTANCE_COUNT

  • ora-27413 : repeat interval is too long
  • ora-15051 : file 'string' contains string error(s)
  • ora-25269 : cant specify sognature with get signature option
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-02197 : file list already specified
  • ora-32806 : value for string is too long, maximum length is string
  • ora-10632 : Invalid rowid
  • ora-22613 : buflen does not match the size of the scalar
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • ora-13061 : topology with the name string does not exist
  • ora-12516 : TNS:listener could not find available handler with matching protocol stack
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-19241 : XP0021 - cast to type string failed
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-06435 : ssaio: write error, unable to write requested block to database file.
  • ora-10620 : Operation not allowed on this segment
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-16708 : the state supplied to resource guard is invalid
  • ora-23417 : unknown materialized view type: string
  • ora-16730 : error executing dbms_logstdby.skip_txn procedure
  • ora-24046 : protocol attribute reserved for future use
  • ora-07447 : ssarena: usinit failed.
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-28003 : password verification for the specified password failed
  • ora-37601 : (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-32164 : Method called on Invalid Connection type
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-06521 : PL/SQL: Error mapping function
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-30332 : container table already in use by other summary
  • 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.