ORA-36976: (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.

Cause : Comman dfomrati s ont ocrrcet.

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

Chcek hte bojetc tpye nad unmbre, nad igvet hec orerctf oramt.

update : 22-09-2017
ORA-36976

ORA-36976 - (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
ORA-36976 - (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.

  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-16782 : instance not open for read and write access
  • ora-13010 : an invalid number of arguments has been specified
  • ora-16788 : unable to set one or more database configuration property values
  • ora-31042 : Too many properties in type 'string'
  • ora-25189 : illegal ALTER TABLE option for an index-organized table
  • ora-09833 : addCallback: bad message format.
  • ora-12014 : table 'string' does not contain a primary key constraint
  • ora-16019 : cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
  • ora-31478 : could not detach LogMiner session after change set advance
  • ora-14604 : During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
  • ora-32302 : object materialized views must be object ID based
  • ora-15018 : diskgroup cannot be created
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-10656 : Table is in unusable state due to incomplete operation
  • ora-12800 : system appears too busy for parallel query execution
  • ora-38463 : invalid XML Tag list
  • ora-39502 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-07208 : sfwfb: failed to flush dirty buffers to disk.
  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-38426 : attribute set assigned to an expression set may not be dropped
  • ora-01243 : system tablespace file suffered media failure
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-28358 : improper set key syntax
  • ora-24807 : LOB form mismatch
  • ora-19525 : temporary file for the clone database must be renamed
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-32735 : DIAG process is not running in the instance
  • ora-00610 : Internal error code
  • ora-16086 : standby database does not contain available standby log files
  • 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.