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 : 17-08-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-08441 : closed parenthesis missing in picture mask
  • ora-29828 : invalid name for implementation type
  • ora-00282 : UPI string call not supported, use ALTER DATABASE RECOVER
  • ora-01254 : cannot end online backup - file string in recovery manager backup
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-16057 : DGID from server not in Data Guard configuration
  • ora-31620 : file or device "string" cannot be specified for string operation
  • ora-19757 : could not resize change tracking file to string blocks
  • ora-22314 : method information mismatch in ALTER TYPE
  • ora-24350 : OCI call not allowed
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-02720 : osnfop: shmat failed
  • ora-31221 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd.
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-39304 : conflicting changes to object "string" : string
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-29824 : operator is invalid
  • ora-25193 : cannot use COMPRESS option for a single column key
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • ora-25145 : allocation policy already specified
  • ora-07402 : sprst: cannot restore user signal handler.
  • ora-02192 : PCTINCREASE not allowed for rollback segment storage clauses
  • ora-09272 : remote os logon is not allowed
  • ora-07489 : scgrcl: cannot get lock status.
  • ora-01308 : initialization parameter utl_file_dir is not set
  • ora-23473 : replication RPC processing for "string"."string" is disabled
  • ora-32823 : subscriber exists for queue string and destination string
  • ora-27416 : BYDAY= clause in repeat interval or calendar contains an invalid weekday
  • ora-06144 : NETTCP: SID (database) is unavailable
  • ora-13618 : The specified value is not a valid value for procedure argument 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.