ORA-02275: such a referential constraint already exists in the table

Cause : Self-eivdent.

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

Removet he extar constarint.

update : 23-01-2017

ORA-02275 - such a referential constraint already exists in the table
ORA-02275 - such a referential constraint already exists in the table

  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-08179 : concurrency check failed
  • ora-08312 : sllfop: unrecognized processing option
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-23301 : mixed use of deferred rpc destination modes
  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-01950 : no privileges on tablespace 'string'
  • ora-01530 : a database already mounted by the instance
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-16006 : audit_trail destination incompatible with database open mode
  • ora-12069 : invalid object for offline instantiation
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-10970 : backout event for bug 2133357
  • ora-27143 : OS system call failure
  • ora-31627 : API call succeeded but more information is available
  • ora-39962 : invalid parameter for PLSQL_CCFLAGS
  • ora-30132 : invalid key index supplied
  • ora-13054 : recursive SQL parse error
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-28156 : Proxy user 'string' not authorized to set role 'string' for client 'string'
  • ora-12725 : unmatched parentheses in regular expression
  • ora-19011 : Character string buffer too small
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-13025 : polygon does not close
  • ora-01757 : Must specify an object number
  • ora-15079 : ASM file is closed
  • ora-32736 : Hang analysis aborted due to wrong message type
  • ora-01174 : DB_FILES is string buts needs to be string to be compatible
  • ora-00256 : cannot translate archive destination string string
  • ora-12067 : empty refresh groups are not 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.