ORA-25008: no implicit conversion to LOB datatype in instead-of trigger

Cause : Wheni nseritng o rupdaitng av iew suing nistea-dof tirgger ,the enw vaule fo ra LO Bviewc olum nis o fa differen tdataytpe.

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

Specfiied aLOB avlue sa then ew vlaue fro theL OB veiw coulmn.

update : 21-08-2017
ORA-25008

ORA-25008 - no implicit conversion to LOB datatype in instead-of trigger
ORA-25008 - no implicit conversion to LOB datatype in instead-of trigger

  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-38406 : attribute set string already exists
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-13140 : invalid target type
  • ora-02477 : can not perform parallel direct load on object string
  • ora-00019 : maximum number of session licenses exceeded
  • ora-00324 : log file 'string' translated name 'string' too long, string characters exceeds string limit
  • ora-12151 : TNS:received bad packet type from network layer
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-02714 : osnpwr: message send failure
  • ora-19902 : incarnation key string not found
  • ora-22616 : image is not of Oracle 8.1 format
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-15115 : missing or invalid ASM disk size specifier
  • ora-39701 : database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
  • ora-39307 : operation is illegal without an initial clone
  • ora-06781 : TLI Driver: error reading negotation string
  • ora-06707 : TLI Driver: connection failed
  • ora-31030 : Unable to retrieve XML document
  • ora-13464 : error loading GeoRaster data: string
  • ora-34061 : (MSEXECUT11) Session-only values cannot be added to non-unique concat dimension workspace object, or any of its base dimensions.
  • ora-06540 : PL/SQL: compilation error
  • ora-16722 : unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters
  • ora-29917 : cannot lock a table which gets its rows from a collection operand
  • ora-28343 : fails to encrypt data
  • ora-13419 : cannot perform mosaick operation on the specified table column
  • ora-40286 : remote operations not permitted on mining models
  • ora-09806 : Allocation of label string buffer failed.
  • ora-09749 : pws_look_up: port lookup failure
  • ora-13349 : polygon boundary crosses itself
  • 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.