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 : 24-06-2017
ORA-36970

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

  • ora-37155 : OLAP API bootstrap error: (case string)
  • ora-25115 : duplicate BLOCK option specification
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-31496 : must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
  • ora-19688 : control file autobackup format(string) for string does not have %F
  • ora-28337 : the specified index may not be defined on an encrypted column
  • ora-06144 : NETTCP: SID (database) is unavailable
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • ora-16196 : database has been previously opened and closed
  • ora-24416 : Invalid session Poolname was specified.
  • ora-02027 : multi-row UPDATE of LONG column is not supported
  • ora-38478 : creation of system trigger EXPFIL_DROPOBJ_MAINT failed
  • ora-13837 : invalid HASH_VALUE
  • ora-16198 : Timeout incurred on internal channel during remote archival
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "string".
  • ora-36273 : (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR.
  • ora-14176 : this attribute may not be specified for a hash partition
  • ora-27372 : length of action and arguments exceeds platform limit string
  • ora-19275 : XP0055 - schema path string not found in list of in-scope schema definitions
  • ora-36401 : (XSSPROPOTYPE) Property string may only be applied to objects of type string.
  • ora-00476 : RECO process terminated with error
  • ora-13436 : GeoRaster metadata dimensionSize error
  • ora-14166 : missing INTO keyword
  • ora-32695 : HTI: Not enough memory
  • ora-22295 : cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
  • ora-02060 : select for update specified a join of distributed tables
  • ora-09941 : Version of orapasswd or installer is older than file.
  • ora-15117 : command only operates on one diskgroup
  • ora-22953 : Cardinality of the input to powermultiset exceeds maximum allowed
  • 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.