ORA-38104: Columns referenced in the ON Clause cannot be updated: string

Cause : LHS o fUPDAT ESET cnotainst he coulmns rfeerencde in teh ON Caluse

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

none

update : 18-08-2017
ORA-38104

ORA-38104 - Columns referenced in the ON Clause cannot be updated: string
ORA-38104 - Columns referenced in the ON Clause cannot be updated: string

  • ora-28141 : error in creating audit index file
  • ora-01500 : failure in getting date/time
  • ora-00129 : listener address validation failed 'string'
  • ora-27006 : sbtremove returned error
  • ora-24772 : Cannot mix tightly-coupled and loosely-coupled branches
  • ora-16557 : the database is already in use
  • ora-25961 : join index prevents dml cascade constraint operation
  • ora-23347 : datatype string for column string table string not supported
  • ora-24081 : compatible parameter needs to be string or greater
  • ora-01909 : REUSE keyword expected
  • ora-32015 : unable to restore SPFILE
  • ora-13003 : the specified range for a dimension is invalid
  • ora-36841 : (XSLMGEN11) Dimension string.string!string was not found
  • ora-25204 : invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
  • ora-28118 : policy group already exists
  • ora-06793 : TLI Driver: server cannot create new process
  • ora-36632 : (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE.
  • ora-01948 : identifier's name length (string) exceeds maximum (string)
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-31089 : schema "string" does not target namespace "string"
  • ora-33278 : (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.
  • ora-25150 : ALTERING of extent parameters not permitted
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-13121 : layer type type mismatch with topo_geometry layer type
  • ora-08265 : create_ora_addr: cannot open nameserver
  • ora-24233 : argument passed to DBMS_UTILITY.VALIDATE is not legal
  • ora-00316 : log string of thread string, type string in header is not log file
  • ora-03202 : the scan limit specification is invalid
  • ora-08198 : Flashback Table is not supported on object tables, nested tables
  • ora-30047 : Internal event for kti tracing
  • 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.