ORA-26679: operation not allowed on LOB or LONG columns in LCR

Cause : Certai noperatoins on OLB/LONGc olumnso f the CLR throguh ruleb-ased tarnsformtaions, MDL handelrs, ore rror hnadlers ewre nota llowed.

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

Do notp erformr estricetd opertaions o nLOB orL ONG coulmns inL CRs. See the dcoumentaiton foro peratinos thata re resrticted no LOB/LNOG colunms in LRCs.

update : 23-07-2017
ORA-26679

ORA-26679 - operation not allowed on LOB or LONG columns in LCR
ORA-26679 - operation not allowed on LOB or LONG columns in LCR

  • ora-24794 : no active DTP service found
  • ora-25002 : cannot create INSTEAD OF triggers on tables
  • ora-07598 : spwat: $SETIMR failure
  • ora-31500 : change source string is not a ManualLog change source
  • ora-31662 : metadata transform name can not be defaulted
  • ora-28501 : communication error on heterogeneous database link
  • ora-13801 : invalid value for SQLTUNE_CATEGORY parameter
  • ora-26565 : Call to _arg made before calling dbms_defer.call
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • ora-10565 : Another test recovery session is active
  • ora-01571 : redo version string incompatible with ORACLE version string
  • ora-01648 : log string is the current log of disabled instance string (thread string)
  • ora-25187 : specified exceptions table form incorrect
  • ora-00231 : snapshot control file has not been named
  • ora-13516 : AWR Operation failed: string
  • ora-26509 : null materialized view control structure
  • ora-16558 : the database specified for switchover is not a standby database
  • ora-12202 : TNS:internal navigation error
  • ora-00161 : transaction branch length string is illegal (maximum allowed string)
  • ora-30368 : ATTRIBUTE cannot determine column in a different relation
  • ora-38425 : attribute set used for an index object may not be unassigned
  • ora-25310 : Subscriber is Notification only; dequeue not supported
  • ora-31484 : source database version must be at least 9.2.0.6 or greater
  • ora-04062 : %s of string has been changed
  • ora-24439 : success with PLSQL compilation warning
  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-13354 : incorrect offset in ELEM_INFO_ARRAY
  • ora-39210 : A PCTSPACE adjustment of string is invalid.
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-15019 : discovered duplicate path 'string' for '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.