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 : 26-07-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-01901 : ROLLBACK keyword expected
  • ora-14273 : lower-bound partition must be specified first
  • ora-02153 : invalid VALUES password string
  • ora-14617 : cannot add/drop values to DEFAULT subpartition
  • ora-28667 : USING INDEX option not allowed for the primary key of an IOT
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-12561 : TNS:unknown error
  • ora-06446 : ssvpstevrg: Failed with unexpected error number.
  • ora-38727 : FLASHBACK DATABASE requires a current control file.
  • ora-30453 : summary contains AVG without corresponding COUNT
  • ora-26500 : error on caching "string"."string"
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-02420 : missing schema authorization clause
  • ora-10940 : trace name context forever
  • ora-12810 : PARALLEL_MAX_SERVERS must be less than or equal to string
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-25269 : cant specify sognature with get signature option
  • ora-03209 : DBMS_ADMIN_PACKAGE invalid file/block specification
  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-06400 : NETCMN: No default host string specified
  • ora-16958 : DML statements running parallel are not supported for test execute.
  • ora-24763 : transaction operation cannot be completed now
  • ora-00482 : LMD* process terminated with error
  • ora-31490 : could not attach to LogMiner session
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-40226 : model upgrade/downgrade must be performed by SYS
  • ora-26086 : direct path does not support triggers
  • ora-38784 : Cannot create restore point '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.