ORA-29930: COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause

Cause : The CMOPUTE NACILLAYR DATAo ptionw as spceifiedw ithou tthe WTIH INDXE CONTXET clasue.

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

Speciyf the IWTH INEDX CONETXT opiton.

update : 29-04-2017

ORA-29930 - COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
ORA-29930 - COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause

  • ora-01438 : value larger than specified precision allowed for this column
  • ora-06737 : TLI Driver: connection failed
  • ora-00702 : bootstrap verison 'string' inconsistent with version 'string'
  • ora-39168 : Object path string was not found.
  • ora-16201 : Skip procedure requested to apply statement
  • ora-10589 : Test recovery had to corrupt string data blocks in order to proceed
  • ora-02335 : invalid datatype for cluster column
  • ora-22064 : invalid NLS parameter string [string]
  • ora-31411 : change set string is referenced by a change table
  • ora-14612 : Duplicate lob segment name string for lob column string in template
  • ora-31493 : could not prepare session for LogMiner session
  • ora-08465 : input mask contains more than 32 characters
  • ora-27433 : cannot alter state of step string for job string.string to string
  • ora-19921 : maximum number of string rows exceeded
  • ora-21703 : cannot flush an object that is not modified
  • ora-06575 : Package or function string is in an invalid state
  • ora-13333 : invalid LRS measure
  • ora-31465 : cannot obtain a lock on the subscription
  • ora-23328 : mview base table "string"."string" differs from master table "string"."string"
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-29909 : label for the ancillary operator is not a literal number
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-29385 : cannot create plan directive from string to string
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-13024 : polygon has less than three segments
  • ora-16174 : user requested thread/sequence termination of managed recovery
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-09958 : IMON: two processes with the same ORACLE pid are active
  • 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.