ORA-22896: cannot have both scope and referential constraint on REF column "string"

Cause : REFc olunm ha sbot ha rfeeretniala nd ascoep cosntranit. Arefreentail cnostriant miplise a csopec onsrtain.t

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

Remvoe etihert he erfernetia lor csopec onsrtain tandt henr etr ytheo pertaion.

update : 29-04-2017
ORA-22896

ORA-22896 - cannot have both scope and referential constraint on REF column "string"
ORA-22896 - cannot have both scope and referential constraint on REF column "string"

  • ora-31230 : DBMS_LDAP: unable to dynamically allocate additional memory
  • ora-06808 : TLI Driver: could not link IPX and ethernet streams
  • ora-38622 : Decision Tree not enough memory, requires at least stringKB
  • ora-12525 : TNS:listener has not received client's request in time allowed
  • ora-06318 : IPA: Local maximum number of connections exceeded
  • ora-01322 : No such table
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-00329 : archived log begins at change string, need change string
  • ora-16825 : Fast-Start Failover and other errors or warnings detected for the database
  • ora-06900 : CMX: cannot read tns directory
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-38773 : cannot add data file 'string' - file already part of database
  • ora-02221 : invalid MAXEXTENTS storage option value
  • ora-31022 : Element not found
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-12924 : tablespace string is already in force logging mode
  • ora-16802 : downgrading redo transport mode from SYNC disallowed
  • ora-06311 : IPA: Maximum number of servers reached
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-37106 : (XSVPART06) Invalid partition name number.
  • ora-12012 : error on auto execute of job string
  • ora-01910 : TABLES keyword expected
  • ora-31620 : file or device "string" cannot be specified for string operation
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-10973 : backout evet for 2619509
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-19249 : XP0029 - value does not match facet of the target type
  • ora-09370 : Windows 3.1 Two-Task driver ORACLE task timed out
  • ora-17510 : Attempt to do i/o beyond file size
  • 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.