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 : 24-06-2017
ORA-23339

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

  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-24440 : OCI Easy Install mode cannot be initialized
  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-24433 : This statement has already been prepared using OCIStmtPrepare2.
  • ora-40102 : invalid input string for data mining operation string
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-00089 : invalid instance number in ORADEBUG command
  • ora-32317 : cannot run a job from a job
  • ora-02777 : Stat failed on log directory
  • ora-03282 : missing ALLOCATE EXTENT option
  • ora-29353 : The transportable list is too long.
  • ora-06514 : PL/SQL: The remote call cannot be handled by the server
  • ora-29309 : export dump file was generated by different version of DBMS_PITR package
  • ora-25248 : duplicate agent specified in the agent list
  • ora-01187 : cannot read from file string because it failed verification tests
  • ora-24006 : cannot create QUEUE, string already exists
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-30679 : JDWP-based debugging not supported in this configuration
  • ora-39700 : database must be opened with UPGRADE option
  • ora-36376 : (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-16598 : Data Guard broker detected a mismatch in configuration
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-01084 : invalid argument in OCI call
  • ora-24852 : protocol error during statement execution
  • ora-01607 : cannot add logfile to the specified instance
  • ora-24814 : operation not allowed for temporary LOBs
  • ora-16123 : transaction string string string is waiting for commit approval
  • ora-09354 : Windows 32-bit Two-Task driver: ORACLE task unexpectedly died
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • 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.