ORA-36650: (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.

Cause : Unique concat base dimensions cannot contain duplicate values.

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

Use MAINTAIN RENAME to change one of the duplicate values and retry.

update : 26-06-2017
ORA-36650

ORA-36650 - (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.
ORA-36650 - (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.

  • ora-00282 : UPI string call not supported, use ALTER DATABASE RECOVER
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-25256 : consumer cannot be specified with a single-consumer queue or an exception queue
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-28333 : column is not encrypted
  • ora-00103 : invalid network protocol; reserved for use by dispatchers
  • ora-16529 : bad sender id
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-09813 : Unable to get directory status
  • ora-13434 : GeoRaster metadata cellRepresentation error
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-37101 : (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
  • ora-28182 : cannot acquire Kerberos service ticket for client
  • ora-12593 : TNS:no registered connection
  • ora-12041 : cannot record ROWIDs for index-organized table "string"."string"
  • ora-19034 : Type not supported during schema generation
  • ora-07203 : sltln: attempt to translate a long environment variable.
  • ora-32615 : incorrect use of MODEL IS ANY predicate
  • ora-28180 : multiple authentication methods provided by proxy
  • ora-07218 : slkhst: could not perform host operation
  • ora-23490 : extension request "string" with status "string" not allowed in this operation
  • ora-16212 : number processes specified for APPLY is too great
  • ora-32054 : lost communication with FMPUTL process
  • ora-09855 : removeCallback: bad message format.
  • ora-27480 : window "string" is currently open
  • ora-23370 : table string and table string are not shape equivalent (string)
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-12051 : ON COMMIT attribute is incompatible with other options
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-03278 : duplicate ALLOCATE EXTENT option specification
  • 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.