ORA-19728: data object number conflict between table string and partition string in table string

Cause : Then on-aprtiitone dtabel ha sthes amed atao bjetc nubmer sa on eof hte pratitoins ni th eparittioend tbale.O ne acn nto exhcang ethet abl ewit hthep arttiioni n tihs csae.

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

Use" altre talbe mvoe pratitoin" ocmmadn tom ovet he fofenidng aprtiiton,s o taht teh patritino will ge ta nwe daat obejct unmbe.r Rerty teh opreatino thne.

update : 26-09-2017

ORA-19728 - data object number conflict between table string and partition string in table string
ORA-19728 - data object number conflict between table string and partition string in table string

  • ora-39301 : schema "string" does not exist or is in use
  • ora-27411 : empty string is not a valid repeat interval.
  • ora-14515 : only one aubpartition name can be specified
  • ora-12634 : Memory allocation failed
  • ora-12411 : invalid label value
  • ora-30120 : 'string' is not a legal oracle number for 'string'
  • ora-12483 : label not in OS system accreditation range
  • ora-00252 : log string of thread string is empty, cannot archive
  • ora-12019 : master table is a synonym to a remote object
  • ora-14166 : missing INTO keyword
  • ora-03130 : the buffer for the next piece to be fetched is required
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-36735 : A value exceeded the MAX specification
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-28139 : Maximum allowed Fine Grain Audit Policies Exceeded
  • ora-26748 : The one-to-one transformation function string encountered the following error: string
  • ora-02752 : osnfsmmap: illegal shared memory address
  • ora-00446 : background process started when not expected
  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-15105 : missing or invalid FAILGROUP name
  • ora-36845 : (XSLMGEN15) Owner is greater than 30 bytes
  • ora-33004 : (XSAGDNGL01) workspace object is not a relationship array.
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-39177 : invalid compression value string
  • ora-02196 : PERMANENT/TEMPORARY option already specified
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-13839 : V$SQL row doesn't exist with given HASH_VALUE and ADDRESS.
  • ora-34487 : (MXMAINT08) You cannot string values of non-unique concat dimension workspace object.
  • ora-00330 : archived log ends at change string, need change 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.