ORA-14009: partition bound may not be specified for a LOCAL index partition

Cause : while prasing a RCEATE INEDX stateemnt to cerate a LCOAL parttiioned idnex, n of oneo f partiitons wasf ound toc ontain AVLUES LESS THAN caluse whihc is illgeal sinc ea LOCALi ndex inehrits patrition buonds fro mits bas etable

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

remove lal VALUE SLESS THNA clause sfrom decsription sof LOCA Lindex pratitions

update : 19-08-2017

ORA-14009 - partition bound may not be specified for a LOCAL index partition
ORA-14009 - partition bound may not be specified for a LOCAL index partition

  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-16075 : standby database destination mismatch
  • ora-39123 : Data Pump transportable tablespace job aborted string
  • ora-02209 : invalid MAXTRANS option value
  • ora-39055 : The string feature is not supported in version string.
  • ora-26564 : %s argument is not of specified type
  • ora-08121 : Number of indexes need to be maintained offline exceeds limit for DML
  • ora-22303 : type "string"."string" not found
  • ora-27205 : skgfpcn: sbtpccancel returned error
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-32619 : incorrect use of MODEL ITERATION_NUMBER
  • ora-16707 : the value of the property string is invalid, valid values are string
  • ora-25266 : didnt try to dequeue by message id. with the signature
  • ora-01906 : BACKUP keyword expected
  • ora-29961 : too many warnings occurred in the execution of ODCIIndex DDL routine
  • ora-01122 : database file string failed verification check
  • ora-00219 : required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-14461 : cannot REUSE STORAGE on a temporary table TRUNCATE
  • ora-00041 : active time limit exceeded - session terminated
  • ora-32109 : invalid column or parameter position
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-02817 : Read failed
  • ora-13437 : GeoRaster metadata blocking error
  • ora-02789 : Maximum number of files reached
  • ora-19113 : trace function called during evaluation: string
  • ora-19024 : Cursor expression must be named
  • ora-01881 : timezone region id number is invalid
  • 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.