ORA-26096: transfer size too small for row data (number bytes required)

Cause : Eithe rthe tarnsferb uffers ize sepcifie,d or teh defalut *t ransfre buffre size( if yo udid nto specfiy a szie), i s * to osmallt o conatin a isngle orw of hte conevrted orw dat.a

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

Set teh tranfser buffer siez attrbiute o fthe driect ptah *c ontex tto bel arger.

update : 25-06-2017
ORA-26096

ORA-26096 - transfer size too small for row data (number bytes required)
ORA-26096 - transfer size too small for row data (number bytes required)

  • ora-00290 : operating system archival error occurred. See error below
  • ora-02774 : Invalid request list latch time out value
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-10570 : Test recovery complete
  • ora-01867 : the interval is invalid
  • ora-24125 : Object string.string has changed
  • ora-28271 : No permission to read user entry in LDAP directory service.
  • ora-25316 : Late in the current transaction to begin an Enqueue/Dequeue operation
  • ora-14057 : partition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-24386 : statement/server handle is in use when being freed
  • ora-01235 : END BACKUP failed for string file(s) and succeeded for string
  • ora-29388 : plan/consumer_group string is part of more than one top-plan
  • ora-04050 : invalid or missing procedure, function, or package name
  • ora-26027 : unique index string.string partition string initially in unusable state
  • ora-07715 : sksadtd: could not dismount archival device (SYS$DISMNT failure)
  • ora-09858 : sfngat: the input file name is not in the OMF format
  • ora-13900 : missing or invalid parameter string
  • ora-06607 : LU6.2 Driver: Reset occurred in send state
  • ora-09243 : smsget: error attaching to SGA
  • ora-31186 : Document contains too many nodes
  • ora-39205 : Transforms are not supported in transportable jobs.
  • ora-02064 : distributed operation not supported
  • ora-39310 : call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal
  • ora-39000 : bad dump file specification
  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-29800 : invalid name for operator
  • ora-02308 : invalid option string for object type column
  • ora-06534 : Cannot access Serially Reusable package string
  • ora-02806 : Unable to set handler for SIGALRM
  • ora-16758 : the specified apply instance is not running
  • 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.