ORA-22879: cannot use the LOB INDEX clause for partitioned tables

Cause : An attempt was made to specify a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned table.

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

Remove the LOB INDEX clause.

update : 24-06-2017
ORA-22879

ORA-22879 - cannot use the LOB INDEX clause for partitioned tables
ORA-22879 - cannot use the LOB INDEX clause for partitioned tables

  • ora-14641 : STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-30189 : reserved for future use
  • ora-06124 : NETTCP: timeout waiting for ORASRV
  • ora-10573 : Test recovery tested redo from change string to string
  • ora-29828 : invalid name for implementation type
  • ora-12731 : invalid collation class in regular expression
  • ora-24087 : Invalid database user string
  • ora-00125 : connection refused; invalid presentation
  • ora-13197 : element string.string.string is out of range
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-16586 : could not edit database property through instance
  • ora-30748 : column string already enabled to store objects of type string.string
  • ora-33094 : (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.
  • ora-14255 : table is not partitioned by Range, Composite Range or List method
  • ora-07218 : slkhst: could not perform host operation
  • ora-27004 : invalid blocksize specified
  • ora-16039 : RFS request version mismatch
  • ora-28052 : the account is disabled
  • ora-07631 : smcacx: $EXPREG failure
  • ora-08102 : index key not found, obj# string, file string, block string (string)
  • ora-01600 : at most one "string" in clause "string" of string
  • ora-29378 : invalid consumer group mapping priorities
  • ora-29931 : specified association does not exist
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-29809 : cannot drop an operator with dependent objects
  • ora-12202 : TNS:internal navigation error
  • ora-15202 : cannot create additional ASM internal change segment
  • 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.