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 : 16-08-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-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-34361 : (MXDSS12) number other user reading
  • ora-26508 : null materialized view connection
  • ora-19025 : EXTRACTVALUE returns value of only one node
  • ora-16503 : site ID allocation failure
  • ora-06420 : NETCMN: SID lookup failure
  • ora-01309 : invalid session
  • ora-13769 : Snapshots string and string do not exist.
  • ora-14123 : duplicate NOREVERSE clause
  • ora-25500 : database is not open
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-10997 : another startup/shutdown operation of this instance inprogress
  • ora-16752 : resource guard could not mount standby database
  • ora-28265 : NameSpace beginning with 'sys_' is not allowed
  • ora-32121 : Source FILE is null
  • ora-37104 : (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-36804 : (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
  • ora-36838 : (XSLMGEN08) Dimension string.string!string attribute string is missing a COLUMNNAME property value
  • ora-26753 : Mismatched columns found in 'string.string'
  • ora-39023 : Version string is not supported.
  • ora-23386 : replication parallel push cannot create slave processes
  • ora-39068 : invalid master table data in row with PROCESS_ORDER=string
  • ora-30945 : Could not create mapping table 'string'
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-25220 : enqueue failed, signature not specified for a non-repudiable queue
  • ora-32624 : illegal reordering of MODEL dimensions
  • ora-12924 : tablespace string is already in force logging mode
  • ora-29557 : Java system class string cannot be modified
  • 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.