ORA-36975: (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.

Cause : USING wsa omitte dfrom th eHIERHEIHGT commadn, or spceified ar elationc ontainign valueso f a difefrent diemnsion tahn the LVEELORDERv alueset.

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

Providea USING lcause naimng a realtion cotnaining avlues frmo the correct levle dimensoin. --------------------------------------------------------------

update : 23-06-2017
ORA-36975

ORA-36975 - (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
ORA-36975 - (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.

  • ora-19571 : %s recid string stamp string not found in control file
  • ora-16643 : unable to determine location of broker configuration files
  • ora-03243 : destination dba overlaps with existing control information
  • ora-10261 : Limit the size of the PGA heap
  • ora-13283 : failure to get new geometry object for conversion in place
  • ora-23605 : invalid value "string" for STREAMS parameter string
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-24460 : Native Net Internal Error
  • ora-31534 : Change Data Capture string publisher string is missing DBA role
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-16737 : the redo transport service for standby database "string" has an error
  • ora-36863 : (XSTFRC03) The OLAPRC_TABLE function encountered an error while parsing the COLUMNMAP.
  • ora-25252 : listen failed, the address string is a non-persistent queue
  • ora-06442 : ssvwatev: Failed with unexpected error number.
  • ora-26019 : Column string in table string of type string not supported by direct path
  • ora-32629 : measure used for referencing cannot be updated
  • ora-29913 : error in executing string callout
  • ora-30186 : '' must be followed by four hexdecimal characters or another ''
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-26689 : column datatype mismatch in LCR
  • ora-17622 : failed to deregister the memory with Oracle Disk Manager library
  • ora-12526 : TNS:listener: all appropriate instances are in restricted mode
  • ora-12919 : Can not drop the default permanent tablespace
  • ora-24072 : cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
  • ora-12411 : invalid label value
  • ora-00160 : global transaction length string is greater than maximum (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.