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 : 17-08-2017

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-23463 : flavor incompatible with object "string"."string"
  • ora-09763 : osnmpx: send/receive error exchanging Mach ports.
  • ora-02186 : tablespace resource privilege may not appear with other privileges
  • ora-38503 : index already defined using the parameters
  • ora-29361 : value string is outside valid range of 0 to 100
  • ora-24440 : OCI Easy Install mode cannot be initialized
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-40306 : wide data not supported for decision tree model create
  • ora-12667 : Shared server: outbound transport protocol different from inbound
  • ora-27216 : skgfgsmcs: sbtinfo2 returned a malformed response
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-06111 : NETTCP: disconnect failure
  • ora-24326 : handle passed in is already initialized
  • ora-10563 : Test recovery had to corrupt data block (file# string, block# string) in order to proceed
  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-16101 : a valid start SCN could not be found
  • ora-01782 : UNRECOVERABLE cannot be specified for a cluster or clustered table
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-38408 : The ADT "string" does not exist in the current schema.
  • ora-27250 : OS system call failure
  • ora-21601 : attribute is not an object
  • ora-16815 : incorrect redo transport setting for AlternateLocation for standby database "string"
  • ora-24230 : input to DBMS_DDL.WRAP is not a legal PL/SQL unit
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-32163 : Method called on Invalid Environment type
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-00342 : archived log does not have expected resetlogs SCN string
  • ora-02253 : constraint specification not allowed here
  • ora-39959 : invalid warning number (string)
  • ora-19375 : no CREATE TABLE privilege on schema "string"
  • 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.