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 : 22-08-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-01955 : DEFAULT ROLE 'string' not granted to user
  • ora-31195 : XML node 'string' (type=string) does not support this operation
  • ora-06311 : IPA: Maximum number of servers reached
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-13425 : function not implemented
  • ora-24503 : codepoint length overflows for piecewise operation
  • ora-31689 : illegal value for base worker id, string
  • ora-02852 : Invalid critical-section time out value
  • ora-38608 : FI itemset minimum-length(string) should not be greater than maximum length(string)
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-02033 : a cluster index for this cluster already exists
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-18015 : invalid source outline signature
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-31076 : required attribute "string" not specified
  • ora-38420 : invalid stored attribute sub-expression: string
  • ora-29383 : all leaves of top-plan string must be consumer groups
  • ora-16599 : Data Guard broker detected a stale configuration
  • ora-01686 : max # files (string) reached for the tablespace string
  • ora-02234 : changes to this table are already logged
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-26096 : transfer size too small for row data (number bytes required)
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-12032 : cannot use rowid column from materialized view log on "string"."string"
  • ora-01202 : wrong incarnation of this file - wrong creation time
  • ora-10973 : backout evet for 2619509
  • ora-27366 : job "string.string" is not running
  • ora-06762 : TLI Driver: error reading orderly release
  • ora-10931 : trace name context forever
  • 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.