ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table

Cause : The caluse IVNALIDAET or UDPATE GOLBAL IDNEXES si alloewd onl yfor ADD hashs ubparittion ot a copmositep artitoined tbale.

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

Remov eclaus eand riessue poeratino

update : 23-04-2017
ORA-14633

ORA-14633 - Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
ORA-14633 - Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table

  • ora-38450 : error computing a stored attribute for the expression set.
  • ora-26686 : cannot capture from specified SCN
  • ora-24085 : operation failed, queue string is invalid
  • ora-13148 : failed to generate SQL filter
  • ora-16071 : dependency archived log file not found string
  • ora-24776 : cannot start a new transaction
  • ora-25109 : standby lock name space has illegal character 'string'
  • ora-13275 : spatial index creation failure on unsupported type
  • ora-22305 : attribute/method/parameter "string" not found
  • ora-25504 : the system is already in quiesced state
  • ora-06262 : NETNTT: nfconn() failed
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-14642 : Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-14612 : Duplicate lob segment name string for lob column string in template
  • ora-16154 : suspect attribute: string
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-19726 : cannot plug data [string] at level string into database running at compatibility level string
  • ora-37113 : OLAP API initialization error: (string)
  • ora-38740 : Usable blocks value string is not valid.
  • ora-38788 : More standby database recovery is needed
  • ora-12434 : invalid audit type: string
  • ora-07403 : sfanfy: db_writers parameter not valid.
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-12926 : FORCE LOGGING option already specified
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-38856 : cannot mark instance string (redo thread string) as enabled
  • ora-32811 : subscriber string already exists
  • ora-16108 : database is no longer a standby database
  • ora-00269 : specified log file is part of thread string not string
  • ora-38610 : FI "string" name prefix is reserved for frequent itemset counting
  • 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.