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-05-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-26527 : local store callback init phase failed for 'string.string'
  • ora-19672 : media management software returned invalid file status
  • ora-19013 : Cannot create VARRAY columns containing XMLType
  • ora-12401 : invalid label string: string
  • ora-30199 : reserved for future use
  • ora-12899 : value too large for column string (actual: string, maximum: string)
  • ora-01485 : compile bind length different from execute bind length
  • ora-01075 : you are currently logged on
  • ora-23622 : Operation string.string.string is in progress.
  • ora-38420 : invalid stored attribute sub-expression: string
  • ora-02875 : smpini: Unable to get shared memory for PGA
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-13626 : The specified object string is not valid for task string.
  • ora-14632 : cannot specify PARALLEL clause when adding a List subpartition
  • ora-26504 : operation not implemented
  • ora-07534 : scginq: $getlki unexpected return on lockid string
  • ora-31639 : unexpected data found
  • ora-06408 : NETCMN: incorrect message format
  • ora-18002 : the specified outline does not exist
  • ora-32511 : cannot create watchpoint in memory needed by watchpointing code
  • ora-27456 : not all arguments of program "string.string" have been defined
  • ora-13140 : invalid target type
  • ora-15180 : Could not open dynamic library string, error [string]
  • ora-28052 : the account is disabled
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-27062 : could not find pending async I/Os
  • ora-00060 : deadlock detected while waiting for resource
  • ora-07745 : slemcl: $CLOSE failure
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-12086 : table "string"."string" is not an object table
  • 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.