ORA-24810: attempting to write more data than indicated

Cause : While rwiting nito a LBO, mored ata wa ssupplide than nidicate.d

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

If dat ais written in ipeces, hten mak esure taht you od not porvide mroe datai n the ipeces (ucmulatievly), tahn you nidicate.d

update : 24-06-2017

ORA-24810 - attempting to write more data than indicated
ORA-24810 - attempting to write more data than indicated

  • ora-19809 : limit exceeded for recovery files
  • ora-23300 : %s
  • ora-16580 : bad Data Guard NetSlave network link
  • ora-02361 : error while attempting to allocate number bytes of memory
  • ora-06567 : invalid number of values specified
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-28578 : protocol error during callback from an external procedure
  • ora-15125 : ASM file name 'string' contains an invalid template name
  • ora-35074 : (QFHEAD02) EIF file string cannot be read by this version of string.
  • ora-01672 : control file may be missing files or have extra ones
  • ora-02705 : osnpol: polling of communication channel failed
  • ora-02072 : distributed database network protocol mismatch
  • ora-26003 : parallel load not supported for index-organized table string.
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-31624 : A job cannot be modified after it has started.
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-02069 : global_names parameter must be set to TRUE for this operation
  • ora-37076 : (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
  • ora-09883 : Two Task interface: oratab file does not exist
  • ora-01453 : SET TRANSACTION must be first statement of transaction
  • ora-27041 : unable to open file
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-27468 : "string.string" is locked by another process
  • ora-22813 : operand value exceeds system limits
  • ora-15153 : cluster not in rolling upgrade
  • ora-30478 : Specified dimension does not exist
  • ora-39111 : Dependent object type string skipped, base object type string already exists
  • ora-25271 : queue table not found for the given queue
  • ora-01034 : ORACLE not available
  • ora-12070 : cannot offline instantiate materialized view "string"."string"
  • 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.