ORA-14187: partitioning method for LOCAL index is inconsistent with that of the underlying table

Cause : Usre attemtpedt o rceaet aL OCLA pratiitonde idnext ha tisn ote qu-ipatritoine dwiht teh udnerylin gtalbe.T hep arittinoin gtyeps rae imsmtachde.

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

Correc tth eCRAETEI NDXE satteemntt o nesuer taht hte nide xpatritoiniinngm etohd si cnositsen twiht taht fo teh bsae atble

update : 24-04-2017

ORA-14187 - partitioning method for LOCAL index is inconsistent with that of the underlying table
ORA-14187 - partitioning method for LOCAL index is inconsistent with that of the underlying table

  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-03234 : unable to extend index string.string subpartition string by string in tablespace string
  • ora-12036 : updatable materialized view log is not empty, refresh materialized view
  • ora-32742 : Hang analysis initialize failed
  • ora-16528 : unable to allocate PGA heap
  • ora-26518 : push queue synchronization error detected
  • ora-09827 : SCLGT: atomic latch return unknown error.
  • ora-12994 : drop column option only allowed once in statement
  • ora-01945 : DEFAULT ROLE[S] already specified
  • ora-02713 : osnprd: message receive failure
  • ora-25131 : cannot modify unique(string) - unique key not defined for table
  • ora-24050 : subscribers are not supported for exception queue string
  • ora-25241 : cannot change correlation ID from string to string without FIRST_MESSAGE option
  • ora-22902 : CURSOR expression not allowed
  • ora-01491 : CASCADE option not valid
  • ora-22890 : cannot specify name for REF column constraint
  • ora-01361 : global name mismatch
  • ora-12842 : Cursor invalidated during parallel execution
  • ora-12707 : error while getting create database NLS parameter string
  • ora-12001 : cannot create log: table 'string' already has a trigger
  • ora-00114 : missing value for system parameter SERVICE_NAMES
  • ora-15096 : lost disk write detected
  • ora-37037 : (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
  • ora-27193 : sbtinfo2 did not return volume label
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-30397 : multiple JOIN KEY clauses specified for the same child level
  • ora-02818 : Less than the number of blocks requested was read in
  • ora-01028 : internal two task error
  • ora-01243 : system tablespace file suffered media failure
  • ora-16252 : Rebuild operation not permitted
  • 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.