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 : 27-06-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-32637 : Self cyclic rule in sequential order MODEL
  • ora-26092 : only LONG or LOB types can be partial
  • ora-09870 : spini: failure initializing maximum number of open files.
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-29658 : EXTERNAL NAME clause is not compatible with its supertype
  • ora-30197 : reserved for future use
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-29274 : fixed-width multibyte character set not allowed for a URL
  • ora-30199 : reserved for future use
  • ora-30437 : all job queue processes have stopped running
  • ora-40302 : invalid classname string in cost matrix specification
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-02238 : filename lists have different numbers of files
  • ora-23492 : no new sites for extension request "string"
  • ora-07683 : sou2os: $SETPRV reset error
  • ora-29306 : datafile string is not online
  • ora-37003 : (AWLISTALL01) number readers
  • ora-06913 : CMX: error during redirection of connection
  • ora-10582 : The control file is not a backup control file
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-07565 : sldext: $SEARCH failure
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-13186 : fixed tile size tessellation failed
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-24272 : initialization value must be either F or T
  • ora-12639 : Authentication service negotiation failed
  • ora-23307 : replicated schema string already exists
  • ora-28544 : connect to agent failed, probable Net8 administration 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.