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-07-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-02315 : incorrect number of arguments for default constructor
  • ora-16950 : Remote mapped cursors are not supported by this feature.
  • ora-26684 : invalid value for value_type
  • ora-28556 : authorization insufficient to access table
  • ora-02189 : ON required
  • ora-01371 : Complete LogMiner dictionary not found
  • ora-13607 : The specified task or object string already exists
  • ora-33911 : (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
  • ora-16658 : unobserved Fast-Start Failover configuration
  • ora-19288 : XP0017 - invalid number of arguments to function - string
  • ora-12086 : table "string"."string" is not an object table
  • ora-37172 : illegal dimension type
  • ora-14170 : cannot specify clause in CREATE TABLE|INDEX
  • ora-06710 : TLI Driver: send interrupt break message failed
  • ora-03007 : obsolete feature
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-28594 : agent control utility: invalid parameter name
  • ora-07744 : slemcl: invalid error message file handle
  • ora-36393 : (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-29843 : indextype should support atleast one operator
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-12616 : TNS:no event signals
  • ora-28166 : duplicate rolename in list
  • ora-02397 : exceeded PRIVATE_SGA limit, you are being logged off
  • ora-36402 : (XSSPROP03) The property '$string' requires a leading "$" because it is a system-reserved property name.
  • ora-31698 : Error stack buffer size must be specified and must be greater than 0.
  • ora-03248 : Too much of segment creation activity during migration
  • ora-13063 : relationship information table is missing data for feature table [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.