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-07-2017

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-06904 : CMX: no transport address available for remote application
  • ora-14134 : indexes cannot use both DESC and REVERSE
  • ora-31099 : XDB Security Internal Error
  • ora-32516 : cannot wait for ORADEBUG command completion; waited number ms for process string
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-13841 : SQL profile named string already exists for a different signature/category pair
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-19803 : Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)
  • ora-13775 : inconsistent datatype in input cursor
  • ora-09206 : sfrfb: error reading from file
  • ora-16122 : applying large dml transaction at SCN string
  • ora-02757 : osnfop: fork_and_bind failed
  • ora-00324 : log file 'string' translated name 'string' too long, string characters exceeds string limit
  • ora-30676 : socket read or write failed
  • ora-06711 : TLI Driver: error on bind
  • ora-25156 : old style outer join (+) cannot be used with ANSI joins
  • ora-00155 : cannot perform work outside of global transaction
  • ora-00956 : missing or invalid auditing option
  • ora-08111 : a partitioned index may not be coalesced as a whole
  • ora-12672 : Database logon failure
  • ora-29901 : function underlying operator binding does not exist
  • ora-16233 : The table string.string is unsupported now
  • ora-19161 : XP0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-01127 : database name 'string' exceeds size limit of string characters
  • ora-14050 : invalid ALTER INDEX MODIFY PARTITION option
  • ora-22885 : cannot get REF to a non-persistent object
  • ora-26026 : unique index string.string initially in unusable state
  • ora-12561 : TNS:unknown error
  • 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.