ORA-22898: existing scope clause on "string" points to a table other than the one mentioned in the referential constraint

Cause : Table mentioned in the referential integrity constraint is different from the scope table of the REF column.

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

Specify the scope table of the REF column in the referential integrity constraint and then retry the operation.

update : 26-05-2017
ORA-22898

ORA-22898 - existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
ORA-22898 - existing scope clause on "string" points to a table other than the one mentioned in the referential constraint

  • ora-08331 : Wait operation timed out
  • ora-02817 : Read failed
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-29274 : fixed-width multibyte character set not allowed for a URL
  • ora-01119 : error in creating database file 'string'
  • ora-03298 : cannot shrink datafile - file string is under hot backup
  • ora-19852 : error creating services for auxiliary instance string (error string)
  • ora-12470 : NULL or invalid user label: string
  • ora-30045 : No undo tablespace name specified
  • ora-31433 : subscriber view does not exist
  • ora-36961 : Oracle OLAP is not available.
  • ora-38496 : Expression Filter index is not in a valid state
  • ora-31051 : Requested access privileges not supported
  • ora-22922 : nonexistent LOB value
  • ora-14641 : STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
  • ora-30941 : Cannot specify empty URI for non-default namespace 'string'
  • ora-37175 : column string is not a column of source data
  • ora-16599 : Data Guard broker detected a stale configuration
  • ora-13157 : Oracle error ORAstring encountered while string
  • ora-19662 : archived log thread string sequence string could not be verified
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • ora-36996 : (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
  • ora-07263 : sptpa: kill error.
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-29295 : invalid mime header tag
  • ora-15045 : ASM file name 'string' is not in reference form
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-07469 : sppst: mclear error, unable to clear semaphore.
  • ora-09819 : Number exceeds maximum legal value
  • 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.