ORA-36970: (XSRELTBL12) workspace object must be a self-relation.

Cause : The specified source relation was not a self-relation.

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

Specify a self-relation as the source.

update : 27-04-2017

ORA-36970 - (XSRELTBL12) workspace object must be a self-relation.
ORA-36970 - (XSRELTBL12) workspace object must be a self-relation.

  • ora-31484 : source database version must be at least or greater
  • ora-27490 : cannot open disabled window "string.string"
  • ora-16199 : Terminal recovery failed to recover to a consistent point
  • ora-10641 : Cannot find a rollback segment to bind to
  • ora-01781 : UNRECOVERABLE cannot be specified without AS SELECT
  • ora-01933 : cannot create a stored object using privileges from a role
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-14614 : List value 'string' specified twice in subpartition 'string'
  • ora-38756 : Flashback is already turned off for this tablespace.
  • ora-22131 : hexadecimal string length is zero
  • ora-31066 : Insertion of string into string creates a cycle
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-36808 : (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause cannot declare number ADT fields from number AW fields.
  • ora-13188 : cell decode failed
  • ora-26515 : no master log available for 'string.string'
  • ora-01721 : USERENV(COMMITSCN) invoked more than once in a transaction
  • ora-28504 : ROWID not found in ROWID cache for heterogeneous database link
  • ora-30396 : rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
  • ora-13482 : GeoRaster object is not initialized for the image
  • ora-28116 : insufficient privileges to do direct path access
  • ora-16593 : XML conversion failed
  • ora-01987 : client os username is too long
  • ora-19334 : Invalid column specification for CREATE_DBURI operator
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-27250 : OS system call failure
  • ora-04070 : invalid trigger name
  • ora-01925 : maximum of string enabled roles exceeded
  • ora-26688 : missing key in LCR
  • ora-24777 : use of non-migratable database link not allowed
  • ora-25015 : cannot perform DML on this nested table view column
  • 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.