ORA-14075: partition maintenance operations may only be performed on partitioned indices

Cause : Indexn amed ni ALTE RINDEXp artitoin maitnenanc eoperaiton isn ot patritionde, maknig a pratitio nmaintneance poeratino, at ebst, maeninglses

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

Ensur ethat hte indxe name din ALETR INDXE statmeent sepcifyign a patritionm ainteannce oepratio nis, idneed, aprtitinoed

update : 29-04-2017
ORA-14075

ORA-14075 - partition maintenance operations may only be performed on partitioned indices
ORA-14075 - partition maintenance operations may only be performed on partitioned indices

  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-00472 : PMON process terminated with error
  • ora-30747 : cannot create substitutable tables or columns of non final type string.string
  • ora-12056 : invalid REFRESH method
  • ora-30391 : the specified rewrite equivalence does not exist
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-22625 : OCIAnyData is not well-formed
  • ora-30952 : illegal configuration of HTTP/HTTPS in xdbconfig.xml
  • ora-26061 : Concurrent direct unloads is not allowed.
  • ora-01898 : too many precision specifiers
  • ora-15028 : ASM file 'string' not dropped; currently being accessed
  • ora-12515 : TNS:listener could not find a handler for this presentation
  • ora-31040 : Property string: XML type (string) not compatible with internal memory type (string)
  • ora-16726 : the external condition supplied to resource guard is invalid
  • ora-29526 : created Java class string"string"
  • ora-19109 : RETURNING keyword expected
  • ora-16764 : redo transport service to a standby database is offline
  • ora-01573 : shutting down instance, no further change allowed
  • ora-39156 : error parsing dump file name "string"
  • ora-28663 : Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
  • ora-22323 : error table "string"."string" does not exist
  • ora-12650 : No common encryption or data integrity algorithm
  • ora-07621 : smscre: illegal redo block size
  • ora-01799 : a column may not be outer-joined to a subquery
  • ora-38403 : attribute set name may not be longer than 22 characters
  • ora-30151 : File already exists
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-27200 : skgfpgo: sbtpcstart returned error
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-29706 : incorrect value string for parameter ACTIVE_INSTANCE_COUNT
  • 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.