ORA-24504: data length larger than expected

Cause : Incomin gdata lagrer thanr eceivin gbuffer

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

Set OCIM_AXDATA/AMXCHAR_SZIE approrpiately ro removet he settnig

update : 21-09-2017
ORA-24504

ORA-24504 - data length larger than expected
ORA-24504 - data length larger than expected

  • ora-01544 : cannot drop system rollback segment
  • ora-19263 : XQ0043 - duplicate namespace prefix string
  • ora-32025 : %s.string is not a table or view object.
  • ora-32340 : cannot tune the materialized view definition
  • ora-40303 : invalid prior probability specification
  • ora-01291 : missing logfile
  • ora-02727 : osnpop: access error on orapop executable
  • ora-12004 : REFRESH FAST cannot be used for materialized view "string"."string"
  • ora-06761 : TLI Driver: error sending orderly release
  • ora-07394 : unable to append string to text file
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-00296 : maximum number of files (string) exceeded for RECOVER DATAFILE LIST
  • ora-19565 : BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
  • ora-09212 : sfwfbmt: error writing to file
  • ora-30573 : AUTO segment space management not valid for this type of tablespace
  • ora-01290 : cannot remove unlisted logfile string
  • ora-33911 : (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
  • ora-28507 : error in data dictionary view string
  • ora-37086 : %s is not a valueset
  • ora-01289 : cannot add duplicate logfile string
  • ora-38761 : redo log sequence string in thread string, incarnation string could not be accessed
  • ora-24432 : The statement that was returned is not tagged.
  • ora-28356 : invalid open wallet syntax
  • ora-15151 : missing or invalid version number for rolling upgrade or downgrade
  • ora-38439 : invalid operation "string"
  • ora-06712 : TLI Driver: error on accept
  • ora-31667 : parameter name can not be defaulted
  • ora-36223 : (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type
  • ora-02722 : osnpui: cannot send break message to orapop
  • ora-24409 : client cannot understand the object
  • 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.