ORA-24813: cannot send or receive an unsupported LOB

Cause : An attempt was made to send a LOB across the network, but either the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and server are running different versions of Oracle.

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

Use a version of the Oracle that supports the LOB on both the client and the server.

update : 29-04-2017
ORA-24813

ORA-24813 - cannot send or receive an unsupported LOB
ORA-24813 - cannot send or receive an unsupported LOB

  • ora-29834 : REF datatype not supported with operators
  • ora-29346 : invalid tablespace list
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-12990 : duplicate option specified
  • ora-06004 : NETASY: dialogue file open failure
  • ora-25124 : Database link name not allowed.
  • ora-23472 : materialized view "string"."string" must be atomically refreshed
  • ora-28535 : invalid Heterogeneous Services context
  • ora-03131 : an invalid buffer was provided for the next piece
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-22921 : length of input buffer is smaller than amount requested
  • ora-35074 : (QFHEAD02) EIF file string cannot be read by this version of string.
  • ora-24431 : Statement does not exist in the cache
  • ora-07494 : scgcm: unexpected error.
  • ora-30153 : An invalid File Object is passed to the OCIFile function
  • ora-29702 : error occurred in Cluster Group Service operation
  • ora-25448 : rule string.string has errors
  • ora-34896 : (PPMONTHS00) At least 12 month names must be given. Only number were provided.
  • ora-25409 : failover happened during the network operation,cannot continue
  • ora-30397 : multiple JOIN KEY clauses specified for the same child level
  • ora-07671 : $IDTOASC failed translating an integrity category
  • ora-07455 : estimated execution time (string secs), exceeds limit (string secs)
  • ora-02820 : Unable to write the requested number of blocks
  • ora-16512 : parameter exceeded maximum size limit
  • ora-31104 : Cannot find lock with token "string" on "string" for unlock
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-34143 : (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-02713 : osnprd: message receive failure
  • ora-01276 : Cannot add file string. File has an Oracle Managed Files file name.
  • 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.