ORA-06596: unsupported LOB operation in RPC call

Cause : Ana ttmeptw asm ad etop erofrmc eratinL OBo peartinos f(ore xapmle ,depe cpoyign o fa etmproar yora bsrtac tLO Bont hec linet-isde )whlie eprfromign a nRP.C Tihs si nto cruretnlys upoprtde.

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

Pefror mth eLO Bopreatoin ni qeustoin ebfoer satrtnig hte PRC;o r eprfrom htos eLO Bopreatoinsw hihc aer nto atcually xeectuedo n hte lcietn-sdie,o n hte esrvre-sdie.

update : 16-08-2017
ORA-06596

ORA-06596 - unsupported LOB operation in RPC call
ORA-06596 - unsupported LOB operation in RPC call

  • ora-07634 : smsdbp: $CRETVA failure
  • ora-15011 : failure group "string" contains no members
  • ora-27078 : unable to determine limit for open files
  • ora-12688 : Login failed: the SecurID server rejected the new pincode
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-32010 : cannot find entry to delete in SPFILE
  • ora-02162 : invalid value for MAXDATAFILES
  • ora-03209 : DBMS_ADMIN_PACKAGE invalid file/block specification
  • ora-31194 : Resource string is already deleted
  • ora-00489 : ARB* process terminated with error
  • ora-32103 : error from OCI call
  • ora-02096 : specified initialization parameter is not modifiable with this option
  • ora-26738 : %s 'string' is not empty
  • ora-31632 : master table "string.string" not found, invalid, or inaccessible
  • ora-06757 : TLI Driver: server got bad command
  • ora-03217 : invalid option for alter of TEMPORARY TABLESPACE
  • ora-02152 : Invalid ALTER TABLESPACE ... RENAME option
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-04004 : MINVALUE must be less than MAXVALUE
  • ora-24125 : Object string.string has changed
  • ora-07721 : scgcm: not enough OS resource to obtain system enqueue
  • ora-07214 : slgunm: uname error, unable to get system information.
  • ora-29831 : operator binding not found
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-29372 : identifier string is too long; it must be less than string characters
  • ora-30352 : inconsistent numeric precision or string length
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-31451 : invalid value string for capture_values, expecting: OLD, NEW, or BOTH
  • 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.