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 : 24-04-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-21702 : object is not instantiated or has been de-instantiated in cache
  • ora-26532 : replication parallel push simulated site failure
  • ora-13039 : failed to update spatial index for element string.string.string
  • ora-25242 : cannot change subscriber name from string to string without FIRST_MESSAGE option
  • ora-31020 : The operation is not allowed, Reason: 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-06954 : Illegal file name
  • ora-12551 : TNS:missing keyword
  • ora-01139 : RESETLOGS option only valid after an incomplete database recovery
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-03135 : connection lost contact
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-06400 : NETCMN: No default host string specified
  • ora-29303 : user does not login as SYS
  • ora-28263 : Insufficient memory in global context pool
  • ora-19037 : XMLType result can not be a fragment
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-25402 : transaction must roll back
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-06911 : CMX: t_event returns ERROR
  • ora-14053 : illegal attempt to modify string in string statement
  • ora-02824 : Request free list is empty
  • ora-12591 : TNS:event signal failure
  • ora-22317 : typecode number is not legal as a number type
  • ora-12451 : label not designated as USER or DATA
  • ora-00220 : control file not mounted by first instance, check alert log for more info
  • ora-26027 : unique index string.string partition string initially in unusable state
  • ora-22806 : not an object or REF
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-04071 : missing BEFORE, AFTER or INSTEAD OF keyword
  • 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.