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 : 17-08-2017

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

  • ora-30088 : datetime/interval precision is out of range
  • ora-30754 : column or table string stores objects of only one type
  • ora-03287 : invalid FREELIST GROUP specified
  • ora-30129 : invalid function argument received
  • ora-37037 : (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-13273 : dimension metadata table string does not exist
  • ora-17502 : ksfdcre:string Failed to create file string
  • ora-29394 : session id string and serial# string do not exist
  • ora-25455 : evaluation error for rule set: string.string, evaluation context: string.string
  • ora-01879 : the hh25 field must be between 0 and 24
  • ora-14049 : invalid ALTER TABLE MODIFY PARTITION option
  • ora-37151 : MDX parser initialization error
  • ora-07267 : spwat: invalid process number.
  • ora-06261 : NETNTT: nrange() failed
  • ora-29900 : operator binding does not exist
  • ora-27019 : tape filename length exceeds limit (SBTOPMXF)
  • ora-14607 : Tablespace was not specified for previous subpartitions in template but is specified for string
  • ora-36667 : (XSDPART05) string is not a legal CONCAT partition.
  • ora-02075 : another instance changed state of transaction string
  • ora-01137 : data file string is still in the middle of going offline
  • ora-24373 : invalid length specified for statement
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-38491 : could not evaluate subexpression for rowid "string"
  • ora-29308 : view TS_PITR_CHECK failure
  • ora-31159 : XML DB is in an invalid state
  • ora-23350 : maximum number of recursive calls exceeded
  • ora-01622 : thread number must be specified - default not specific
  • ora-19580 : %s conversation not active
  • 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.