ORA-14511: cannot perform operation on a partitioned object

Cause : An attempt was made to perform an operation that is not allowed on partitioned tables or indexes.

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

Retry the command with correct syntax.

update : 24-06-2017
ORA-14511

ORA-14511 - cannot perform operation on a partitioned object
ORA-14511 - cannot perform operation on a partitioned object

  • ora-22620 : buffer size too small to hold the value
  • ora-12801 : error signaled in parallel query server string
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-12463 : undefined group string for policy string
  • ora-26705 : cannot downgrade capture process after Streams data dictionary has been upgraded
  • ora-38472 : VARCHAR representation of the data item is too long.
  • ora-13756 : Cannot update attribute "string".
  • ora-38704 : Checksum error in flashback database log file header.
  • ora-10579 : Can not modify control file during test recovery
  • ora-03128 : connection is in blocking mode
  • ora-30373 : object data types are not supported in this context
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-13303 : failure to retrieve a geometry object from a table
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-01987 : client os username is too long
  • ora-27159 : failure setting process scheduling priority
  • ora-39111 : Dependent object type string skipped, base object type string already exists
  • ora-14116 : partition bound of partition "string" is too long
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-28663 : Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-23532 : tables with different synchronization mechanisms are in the same group
  • ora-07704 : error in archive text: need ':' after device name
  • ora-01277 : file 'string' already exists
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-23492 : no new sites for extension request "string"
  • ora-28356 : invalid open wallet syntax
  • ora-13763 : illegal ranking attribute "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.