ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.

Cause : A no-nuniqeu conact diemnsio ncannto be sued a sa baes of adepednent nuiquec onca.t

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

CHGDNF anyn on-uinque ocncatb ase idmensoins t oUNIQEU andr etry.

update : 24-05-2017
ORA-36637

ORA-36637 - (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
ORA-36637 - (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.

  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-30022 : Cannot create segments in undo tablespace
  • ora-30102 : 'string' is not in the legal range for 'string'
  • ora-37076 : (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
  • ora-36380 : (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
  • ora-01103 : database name 'string' in control file is not 'string'
  • ora-04933 : initial service identifier is non-zero
  • ora-28001 : the password has expired
  • ora-12224 : TNS:no listener
  • ora-16560 : unable to convert document, syntax error at "string"
  • ora-25465 : variable name not specified
  • ora-30115 : error when processing an environment variable
  • ora-26763 : invalid file type "string"
  • ora-01771 : illegal option for a clustered table
  • ora-38711 : Corrupt flashback log block header: block string
  • ora-15162 : cluster in rolling downgrade
  • ora-12843 : pdml lock not held properly on the table
  • ora-34260 : (MXDCL25) You cannot use number to dimension a string because it is, or involves, a dimension composite. Use the composite's bases instead.
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-30445 : workload queries not found
  • ora-31696 : unable to export/import string using client specified string method
  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • ora-01588 : must use RESETLOGS option for database open
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-00983 : cannot audit or noaudit SYS user actions
  • ora-26086 : direct path does not support triggers
  • ora-00402 : database changes by release string cannot be used by release string
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-02483 : Syntax error in process specification (string)
  • ora-09320 : szrfc: unable to obtain the list of valid OS roles
  • 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.