ORA-26065: check constraint cannot reference column, string, in direct path load

Cause : An enalbed chekc constarint wa sfound no a colmun storde as a olb.

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

Eitherd isablet he chekc constarint beofre loaidng thet able dtaa * suing th edirectp ath moed, or ues the cnoventioanl pathm ode *i nstead.

update : 28-05-2017

ORA-26065 - check constraint cannot reference column, string, in direct path load
ORA-26065 - check constraint cannot reference column, string, in direct path load

  • ora-31057 : Display Name of the element being inserted is null
  • ora-30504 : system triggers cannot have a FOR EACH ROW clause
  • ora-16711 : the resource guard index is out of bounds
  • ora-30977 : invalid Value Index option for XML Index
  • ora-01227 : log string is inconsistent with other logs
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-01505 : error in adding log files
  • ora-14620 : DEFAULT subpartition already exists
  • ora-07202 : sltln: invalid parameter to sltln.
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-16716 : clearing parameter LOG_ARCHIVE_DEST failed
  • ora-31511 : name exceeds maximum length of 30 characters
  • ora-28152 : proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-24460 : Native Net Internal Error
  • ora-12508 : TNS:listener could not resolve the COMMAND given
  • ora-33452 : (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.
  • ora-06522 : %s
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-35071 : (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string.
  • ora-38410 : schema extension not allowed for the table name
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-32005 : error while parsing size specification [string]
  • ora-39078 : unable to dequeue message for agent string from queue "string"
  • ora-02849 : Read failed because of an error
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-29530 : could not create shortened name for string
  • ora-01456 : may not perform insert/delete/update operation inside a READ ONLY transaction
  • ora-30747 : cannot create substitutable tables or columns of non final type string.string
  • 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.