ORA-36991: (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.

Cause : There si a conlfict bewteen th ehierarhcy/leve lrelatino and teh levelo rder vlaueset.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Chooseo bjectst hat don ot conlfict.

update : 25-05-2017
ORA-36991

ORA-36991 - (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.
ORA-36991 - (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.

  • ora-16795 : database resource guard detects that database re-creation is required
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-26765 : invalid parameter "string" for downstream capture "string"
  • ora-13834 : name of SQL profile to be cloned must be provided
  • ora-32330 : invalid operation on online redefinition interim table "string"."string"
  • ora-13139 : could not obtain column definition for string
  • ora-12922 : concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
  • ora-19371 : invalid update option
  • ora-04050 : invalid or missing procedure, function, or package name
  • ora-22983 : not a user-defined REF
  • ora-27045 : unable to close the file
  • ora-13828 : generated SQL profile name string already exists
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-01555 : snapshot too old: rollback segment number string with name "string" too small
  • ora-16706 : no resource guard is available
  • ora-07241 : slemrd: read error.
  • ora-31199 : Warning in processing file string
  • ora-01600 : at most one "string" in clause "string" of string
  • ora-13052 : unsupported geometric type for geometry string.string
  • ora-13154 : invalid precision specified
  • ora-39501 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-32827 : Messaging Gateway agent must be shut down
  • ora-01267 : Failure getting date/time
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-31186 : Document contains too many nodes
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-02146 : SHARED specified multiple times
  • ora-16567 : Data Guard broker internal parser error at "string"
  • ora-06017 : NETASY: message receive failure
  • ora-27152 : attempt to post process failed
  • 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.