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 : 21-09-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-13232 : failed to allocate memory during R-tree creation
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-29263 : HTTP protocol error
  • ora-29260 : network error: string
  • ora-02772 : Invalid maximum server idle time
  • ora-25158 : Cannot specify RELY for foreign key if the associated primary key is NORELY
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-01125 : cannot disable media recovery - file string has online backup set
  • ora-16700 : the standby database has diverged from the primary database
  • ora-00090 : failed to allocate memory for cluster database ORADEBUG command
  • ora-06579 : Bind variable not big enough to hold the output value
  • ora-16123 : transaction string string string is waiting for commit approval
  • ora-32500 : Dirname 'string' cannot exceed 'number' characters
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-32619 : incorrect use of MODEL ITERATION_NUMBER
  • ora-12225 : TNS:destination host unreachable
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-30558 : internal error [string] in function based index
  • ora-01545 : rollback segment 'string' specified not available
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-31635 : unable to establish job resource synchronization
  • ora-06574 : Function string references package state, cannot execute remotely
  • ora-24032 : object string exists, index could not be created for queue table string
  • ora-22153 : source variable-length array is not initialized
  • ora-19320 : Host name not specified in HTTP URL
  • ora-28358 : improper set key syntax
  • ora-02083 : database name has illegal character 'string'
  • ora-22305 : attribute/method/parameter "string" not found
  • ora-09769 : osnmbr: cannot send break message
  • 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.