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 : 20-08-2017

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

  • ora-27465 : invalid value string for attribute string
  • ora-02363 : error reading from file: string
  • ora-29291 : file remove operation failed
  • ora-14123 : duplicate NOREVERSE clause
  • ora-14075 : partition maintenance operations may only be performed on partitioned indices
  • ora-04047 : object specified is incompatible with the flag specified
  • ora-23503 : error occurred during IAS instantiation
  • ora-24307 : invalid length for piece
  • ora-16730 : error executing dbms_logstdby.skip_txn procedure
  • ora-07272 : spwat: invalid semaphore set id.
  • ora-39142 : incompatible version number string in dump file "string"
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-14178 : STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes
  • ora-16657 : reinstatement of database in progress
  • ora-25204 : invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
  • ora-22150 : variable-length array has not been initialized
  • ora-31210 : DBMS_LDAP: PL/SQL - LDAP get_dn error.
  • ora-07264 : spwat: semop error, unable to decrement semaphore.
  • ora-39302 : schema clone operation failed
  • ora-28027 : privileged database links may be used by global users
  • ora-12019 : master table is a synonym to a remote object
  • ora-07493 : scgrcl: lock manager error.
  • ora-39119 : worker process interrupt for delete worker processes call by master process
  • ora-31195 : XML node 'string' (type=string) does not support this operation
  • ora-27033 : failed to obtain file size limit
  • ora-02174 : Missing required thread number
  • ora-19244 : XQ0024 - invalid attribute node in element constructor
  • ora-28045 : SSL authentication between database and OID failed
  • ora-24330 : internal OCI error
  • ora-16715 : redo transport-related property string of standby database "string" is inconsistent
  • 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.