ORA-23344: constraint (string.string) does not exist

Cause : A null, misspelled or nonexistent constraint was specified when registering a uniqueness conflict.

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

Register a named constraint for the specified table.

update : 23-06-2017

ORA-23344 - constraint (string.string) does not exist
ORA-23344 - constraint (string.string) does not exist

  • ora-31050 : Access denied
  • ora-00161 : transaction branch length string is illegal (maximum allowed string)
  • ora-22617 : error while accessing the image handle collection
  • ora-23431 : wrong state: string
  • ora-25004 : WHEN clause is not allowed in INSTEAD OF triggers
  • ora-00093 : %s must be between string and string
  • ora-19237 : XP0017 - unable to resolve call to function - string:string
  • ora-06321 : IPA: Cannot reach the remote side
  • ora-16068 : redo log file activation identifier mismatch
  • ora-01265 : Unable to delete string string
  • ora-13402 : the rasterType is null or not supported
  • ora-06514 : PL/SQL: The remote call cannot be handled by the server
  • ora-28039 : cannot validate Kerberos service ticket
  • ora-12590 : TNS:no I/O buffer
  • ora-02096 : specified initialization parameter is not modifiable with this option
  • ora-00485 : DIAG process terminated with error string
  • ora-19764 : database id string does not match database id string in control file
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • ora-38720 : Missing log file number.
  • ora-02314 : illegal use of type constructor
  • ora-16082 : logical standby is not initialized correctly
  • ora-01501 : CREATE DATABASE failed
  • ora-13459 : GeoRaster metadata SRS error
  • ora-23456 : flavor string does not contain "string"
  • ora-24172 : rule set string.string has errors
  • ora-23359 : error on creating a ddl record for a repcatlog record
  • ora-19698 : %s is from different database: id=string, db_name=string
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-16080 : invalid LogMiner session string for APPLY
  • 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.