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 : 28-07-2017

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-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-28046 : Password change for SYS disallowed
  • ora-37118 : The OLAP API library was not preloaded.
  • ora-36612 : (XSLMS01) invalid OLAP message number: value
  • ora-09283 : sllfsk: error skipping records
  • ora-21702 : object is not instantiated or has been de-instantiated in cache
  • ora-00261 : log string of thread string is being archived or modified
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-10925 : trace name context forever
  • ora-00603 : ORACLE server session terminated by fatal error
  • ora-22871 : ALTER TYPE with REPLACE is not allowed for pure incomplete types
  • ora-13146 : could not find table substitution variable string
  • ora-06772 : TLI Driver: error sending command
  • ora-39701 : database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
  • ora-28009 : connection as SYS should be as SYSDBA or SYSOPER
  • ora-09703 : sem_release: cannot release latch semaphore
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-23302 : application raised communication failure during deferred RPC
  • ora-23437 : template authorization already exists for user
  • ora-13615 : The task or object string is greater than the maximum allowable length of 30 characters.
  • ora-12064 : invalid refresh sequence number: string
  • ora-25965 : fact table must be included in the from clause
  • ora-07419 : sfareq: Database writer got error in timing function.
  • ora-26008 : Invalid syntax or bind variable in SQL string for column string. string
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-26078 : file "string" is not part of database being loaded
  • ora-14321 : cannot add/drop values to DEFAULT partition
  • ora-25145 : allocation policy already specified
  • ora-33223 : (CMOVE03) You cannot move a session-only dimension 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.