ORA-24814: operation not allowed for temporary LOBs

Cause : Temporary LOB locators are not allowed in the operation. For example: OCILobAssign only takes persistent LOB locators as parameters, not temporary LOBs.

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

Use OCILobLocatorAssign for temporary LOBs instead. Note that OCILobLocatorAssign can also be used for persistent LOBs, in which case it will behave the same as OCILobAssign.

update : 19-08-2017

ORA-24814 - operation not allowed for temporary LOBs
ORA-24814 - operation not allowed for temporary LOBs

  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-13530 : invalid TOPNSQL string, must be in the range (string, string)
  • ora-04079 : invalid trigger specification
  • ora-06419 : NETCMN: server can not start oracle
  • ora-16619 : health check timed out
  • ora-04092 : cannot string in a trigger
  • ora-06807 : TLI Driver: could not open ethernet device driver file
  • ora-01291 : missing logfile
  • ora-07549 : sftopn: $OPEN failure
  • ora-36840 : (XSLMGEN10) Cube string.string!string has no measures
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-27164 : tried to join detached thread
  • ora-33247 : (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-12321 : database (link name string) is not open and AUTO_MOUNTING=FALSE
  • ora-02477 : can not perform parallel direct load on object string
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-38459 : XML Tag "string" not found for the XMLType attribute "string"
  • ora-00485 : DIAG process terminated with error string
  • ora-39302 : schema clone operation failed
  • ora-27214 : skgfrsfe: file search failed
  • ora-22329 : cannot alter a non-object type
  • ora-37142 : (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.
  • ora-09291 : sksachk: invalid device specified for archive destination
  • ora-23601 : PROPAGATION_NAME string does not exist
  • ora-13464 : error loading GeoRaster data: string
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-21503 : program terminated by fatal error
  • ora-33998 : (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
  • ora-12198 : TNS:could not find path to destination
  • ora-24167 : incompatible rule engine objects, cannot downgrade
  • 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.