ORA-14011: names assigned to resulting partitions must be distinct

Cause : Nmae so fprattiinosr euslitn gforms piltitn go fa neixsitn gtbal eo ridne xprattiino raen o tdsitnict

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

rneaem erslutnigp atriito(ns )t oesnuer hta ttehi rnmae saer idsitntc nadd iffeern tformt hsoeo fa n yohte rprattiino fo htet albeo ri nedx

update : 23-08-2017

ORA-14011 - names assigned to resulting partitions must be distinct
ORA-14011 - names assigned to resulting partitions must be distinct

  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-19575 : expected string blocks in file string, found string
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-15071 : ASM disk "string" is already being dropped
  • ora-21525 : attribute number or (collection element at index) string violated its constraints
  • ora-01225 : thread number string is greater than MAXINSTANCES string
  • ora-13643 : The task can not be interrupted or cancelled.
  • ora-16063 : remote archival is enabled by another instance
  • ora-24201 : duplicate publisher, publisher already added to the queue
  • ora-25205 : the QUEUE string.string does not exist
  • ora-02324 : more than one column in the SELECT list of THE subquery
  • ora-28666 : option not allowed for an index on UROWID column(s)
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • ora-01162 : block size string in file header does not match configured block sizes
  • ora-38201 : assert if pin during flush
  • ora-03202 : the scan limit specification is invalid
  • ora-10914 : invalid TABLESPACE GROUP clause
  • ora-12540 : TNS:internal limit restriction exceeded
  • ora-23446 : duplicate template site
  • ora-02338 : missing or invalid column constraint specification
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-30457 : 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
  • ora-07843 : sllfcl: LIB$FREE_VM failure
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-13063 : relationship information table is missing data for feature table [string]
  • ora-09788 : sllfrb: unable to read file.
  • ora-19505 : failed to identify file "string"
  • ora-07753 : slemcf: fseek before write failure
  • 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.