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

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-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-02353 : files not from the same unload operation
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-02280 : duplicate or conflicting CYCLE/NOCYCLE specifications
  • ora-19754 : error reading from change tracking file
  • ora-12002 : there is no materialized view log on table "string"."string"
  • ora-02297 : cannot disable constraint (string.string) - dependencies exist
  • ora-01125 : cannot disable media recovery - file string has online backup set
  • ora-36838 : (XSLMGEN08) Dimension string.string!string attribute string is missing a COLUMNNAME property value
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-29316 : datafile string been imported twice
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-01925 : maximum of string enabled roles exceeded
  • ora-13158 : Oracle object string does not exist
  • ora-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-06018 : NETASY: message send failure
  • ora-00483 : During shutdown a process abnormally terminated
  • ora-16709 : standby archived log location settings conflict with flash recovery area
  • ora-06976 : X.25 Driver: endpoint creation failure
  • ora-13339 : LRS polygon clipping across multiple rings
  • ora-28021 : cannot grant global roles
  • ora-07346 : slnrm: normalized file name is too long
  • ora-07708 : sksaprs: tape label name buffer too small
  • ora-16594 : %s process discovered that DMON process does not exist
  • ora-12657 : No algorithms installed
  • ora-13860 : Invalid service name
  • ora-30331 : summary does not exist
  • ora-31182 : Too many PL/SQL DOM handles specified
  • 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.