ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself.

Cause : A realtionw as nmaed i na REALTIONc laus eof teh AGGAMP thta is ont a eslf-rleatio.n

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

Namea valdi sel-frelaiton i nthe ERLATINO staetment.

update : 23-06-2017
ORA-33006

ORA-33006 - (XSAGDNGL02) The relation workspace object is not related to itself.
ORA-33006 - (XSAGDNGL02) The relation workspace object is not related to itself.

  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-01350 : must specify a tablespace name
  • ora-22995 : TABLESPACE DEFAULT option is invalid in this context
  • ora-23328 : mview base table "string"."string" differs from master table "string"."string"
  • ora-31514 : change set string disabled due to capture error
  • ora-00068 : invalid value string for parameter string, must be between string and string
  • ora-04028 : cannot generate diana for object stringstringstringstringstring
  • ora-30515 : suspend triggers cannot have BEFORE type
  • ora-06144 : NETTCP: SID (database) is unavailable
  • ora-01072 : cannot stop ORACLE; ORACLE not running
  • ora-15026 : disk 'string' is not an ASM disk
  • ora-15079 : ASM file is closed
  • ora-26572 : %s.string.string: argument string does not match replication catalog
  • ora-13634 : The task string needs to be reset before being re-executed.
  • ora-13455 : GeoRaster metadata TRS error
  • ora-07631 : smcacx: $EXPREG failure
  • ora-30511 : invalid DDL operation in system triggers
  • ora-13372 : failure in modifying metadata for a table with spatial index
  • ora-02491 : missing required keyword ON or OFF in AUTOEXTEND clause
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-00271 : there are no logs that need archiving
  • ora-25231 : cannot dequeue because CONSUMER_NAME not specified
  • ora-39783 : Invalid direct path transaction active
  • ora-09312 : slspool: error spooling file to printer
  • ora-26716 : message limit reached
  • ora-14085 : partitioned table cannot have column with LONG datatype
  • ora-06577 : output parameter not a bind variable
  • ora-16514 : the request was not found
  • ora-13639 : The current operation was interrupted because it timed out.
  • ora-12408 : unsupported operation: 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.