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 : 26-07-2017
ORA-36970

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

  • ora-12334 : database (link name string) is still open
  • ora-30953 : XML minoccurs value (string) violated
  • ora-31115 : XDB configuration error: string
  • ora-12163 : TNS:connect descriptor is too long
  • ora-39952 : only numbers can be specified as range values
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-16116 : no work available
  • ora-36975 : (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
  • ora-07286 : sksagdi: cannot obtain device information.
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-30018 : Create Rollback Segment failed, USN string is out of range
  • ora-01162 : block size string in file header does not match configured block sizes
  • ora-38700 : Limit of string flashback database logs has been exceeded.
  • ora-27451 : %s cannot be NULL
  • ora-12926 : FORCE LOGGING option already specified
  • ora-23372 : type string in table string is unsupported
  • ora-07407 : slbtpd: invalid exponent.
  • ora-19740 : text is longer than string
  • ora-33265 : (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.
  • ora-15156 : cluster in rolling upgrade from version [string] to [string]
  • ora-12735 : Instant Client Light: unsupported client character set string
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-09200 : sfccf: error creating file
  • ora-27198 : skgfpvl: sbtpcvalidate returned error
  • ora-31614 : routine string received this error from string: string
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-24372 : invalid object for describe
  • ora-02336 : column attribute cannot be accessed
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-13499 : %s
  • 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.