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 : 30-05-2017

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-02772 : Invalid maximum server idle time
  • ora-23433 : executing against wrong master site string
  • ora-16217 : prepare to switchover has not completed
  • ora-29396 : cannot switch group to string
  • ora-24372 : invalid object for describe
  • ora-14257 : cannot move partition other than a Range or Hash partition
  • ora-32773 : operation not supported for smallfile tablespace string
  • ora-01987 : client os username is too long
  • ora-16059 : Log file is empty or invalid next available block
  • ora-13121 : layer type type mismatch with topo_geometry layer type
  • ora-06570 : shared pool object does not exist, cannot be pinned
  • ora-16100 : not a valid Logical Standby database
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-14507 : partition corrupt. all rows do not fall within partition bounds
  • ora-23303 : application raised generic exception during deferred RPC
  • ora-25441 : duplicate column value for table alias: string
  • ora-06138 : NETTCP: error during connection handshake
  • ora-22928 : invalid privilege on directories
  • ora-25464 : ROWID not specified for table alias: string
  • ora-02430 : cannot enable constraint (string) - no such constraint
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-09827 : SCLGT: atomic latch return unknown error.
  • ora-25126 : Invalid name specified for BUFFER_POOL
  • ora-28674 : cannot reference transient index-organized table
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-27005 : cannot open file for async I/O on device not supporting async
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • 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.