ORA-23339: duplicate conflict resolution information

Cause : Teh pseicfeidc obmiantoino fc oulm ngoru,p esqeunec,c ofnlcitt yep nado/rp aarmtee rtbal enmae ,praaemtre oclmunn aem,a n dpraaemtre esqeunec unmebrh a sarledayb ene ergsitree.d

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

Vreiyf hta taddiitoanlc ofnlcitr eosltuino nifromtaino enesd ot eb dadde nadp rvoied anwe esqeunec unmebr .I fmdoiyfign xeitsign nifromtaino,t h eeixsitn gifnomraito nmsutb ed rpopde ifrts.

update : 26-04-2017

ORA-23339 - duplicate conflict resolution information
ORA-23339 - duplicate conflict resolution information

  • ora-03205 : partition name is required when partitioned type is specified
  • ora-02219 : invalid NEXT storage option value
  • ora-28020 : IDENTIFIED GLOBALLY already specified
  • ora-34296 : (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
  • ora-39162 : Transportable tablespace job require privileges
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-00827 : could not shrink sga_target to specified value
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-02096 : specified initialization parameter is not modifiable with this option
  • ora-25158 : Cannot specify RELY for foreign key if the associated primary key is NORELY
  • ora-22999 : CLOB or NCLOB data may have been corrupted
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-12023 : missing index on materialized view "string"."string"
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-06540 : PL/SQL: compilation error
  • ora-36982 : (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
  • ora-02353 : files not from the same unload operation
  • ora-31615 : routine string received this error: string
  • ora-28045 : SSL authentication between database and OID failed
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-15199 : Internal ASM tracing event number 15199
  • ora-07741 : slemop: $OPEN failure
  • ora-15170 : cannot add entry 'string' in directory 'string'
  • ora-16591 : unknown field "string" in document
  • ora-38601 : FI Not enough memory for frequent itemset counting: string
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-23621 : Operation corresponding to script string is in progress.
  • ora-13389 : unable to compute buffers or intersections in analysis function
  • ora-00113 : protocol name string is too long
  • 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.