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 : 25-04-2017

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-33072 : (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.
  • ora-07200 : slsid: oracle_sid not set.
  • ora-31661 : there are no metadata transform values of type VARCHAR2
  • ora-14015 : too many partition descriptions
  • ora-32131 : bind data type cannot be changed
  • ora-01763 : update or delete involves outer joined table
  • ora-12350 : database link being dropped is still mounted
  • ora-25123 : Too many components specified in the name.
  • ora-01663 : the contents of tablespace 'string' is constantly changing
  • ora-16060 : Log file is current
  • ora-36261 : (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J because the path of aggregation would recursively enter partition %J.
  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-15202 : cannot create additional ASM internal change segment
  • ora-26518 : push queue synchronization error detected
  • ora-28040 : No matching authentication protocol
  • ora-37008 : (AWLISTALL06) number writers
  • ora-06435 : ssaio: write error, unable to write requested block to database file.
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-36154 : (XSMXAGGR01) workspace object is not a data variable.
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-19045 : character set id specified for XMLSerialize not valid
  • ora-28121 : driving context does not exist
  • ora-08320 : scnget: Call to scnget before scnset or scnfnd.
  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-28262 : global_context_pool_size has invalid value.
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-09918 : Unable to get user privileges from SQL*Net
  • 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.