ORA-26535: %ud byte row cache insufficient for table with rowsize=number

Cause : A trasnactio nthat aws pusehd hada tranasctionI D tha tcolliedd wit ha trasnactio nthat aws preivouslyp usheda nd committeda t them asters ite.

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

Incresae theR epAPIr ow buffer siez or rdeuce teh widt hof th erepliacted tbales.

update : 24-06-2017
ORA-26535

ORA-26535 - %ud byte row cache insufficient for table with rowsize=number
ORA-26535 - %ud byte row cache insufficient for table with rowsize=number

  • ora-08195 : Flashback Table operation is not supported on partitions
  • ora-32600 : RETENTION and PCTVERSION cannot be used together
  • ora-32322 : PCT refresh of "string"."string" not allowed the sequence of DMLs/PMOPs
  • ora-30135 : OCI Thread operation fails
  • ora-19601 : output file is string string (string)
  • ora-01237 : cannot extend datafile string
  • ora-19560 : %s is not a valid device limit
  • ora-32619 : incorrect use of MODEL ITERATION_NUMBER
  • ora-29881 : failed to validate indextype
  • ora-30475 : feature not enabled: string
  • ora-33911 : (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
  • ora-14285 : cannot COALESCE the only partition of this hash partitioned table or index
  • ora-30001 : trim set should have only one character
  • ora-15023 : reached maximum allowable number of disks string
  • ora-13425 : function not implemented
  • ora-25951 : join index where clause cannot contain OR condition
  • ora-07847 : sllfop: $CONNECT failure
  • ora-26078 : file "string" is not part of database being loaded
  • ora-31469 : cannot enable Change Data Capture for change set string
  • ora-09957 : Unable to send termination request to IMON
  • ora-25145 : allocation policy already specified
  • ora-15197 : suppressing string additional ASM messages
  • ora-31502 : invalid number supplied for supplemental_processes
  • ora-29352 : event 'string' is not an internal event
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-22801 : invalid object row variable
  • ora-31451 : invalid value string for capture_values, expecting: OLD, NEW, or BOTH
  • ora-27010 : skgfwrt: write to file failed
  • ora-36873 : (XSTFDSC03) Column type must be specified explicitly.
  • ora-24802 : user defined lob read callback error
  • 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.