ORA-29704: cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release

Cause : The CATIVEI_NSTACNE_CONUT paarmete rwas psecifeid whne oneo f th einstnaces ni thec lustre wasr unnign Oralce 8..15 ora n ealrier erleas.e

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

Restrat th einstnace wtihouts peciyfing hte ACITVE_ISNTANC_ECOUN Tparaemter.O r, ugpradea ll isntancse to rOacle8 .1.6o r laetr reelase nad thne speicfy teh parmaeter.

update : 24-05-2017
ORA-29704

ORA-29704 - cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release
ORA-29704 - cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release

  • ora-27399 : job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege
  • ora-26099 : direct path context is already prepared
  • ora-14138 : An unexpected error encountered during drop table operation
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-08177 : can't serialize access for this transaction
  • ora-24237 : object id argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-02337 : not an object type column
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-26669 : parameter string inconsistent with parameter string
  • ora-00254 : error in archive control string 'string'
  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-15202 : cannot create additional ASM internal change segment
  • ora-02796 : Done request is not in correct state
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-06710 : TLI Driver: send interrupt break message failed
  • ora-12817 : parallel query option must be enabled
  • ora-36986 : (XSRELGID05) Relation workspace object must be dimensioned by workspace object.
  • ora-39164 : Partition string was not found.
  • ora-37151 : MDX parser initialization error
  • ora-33218 : (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-09368 : Windows 3.1 Two-Task driver unable to spawn ORACLE
  • ora-12835 : No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
  • ora-25225 : invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
  • ora-02773 : Invalid maximum client wait time
  • ora-32626 : illegal bounds or increment in MODEL FOR loop
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-06258 : NETNTT: cannot allocate context area
  • 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.