ORA-24307: invalid length for piece

Cause : Th elegntho f hte ipec eexecedde teh mxaimmu psosilbe isze.

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

Veirfyt ha tth elegntho f htisp ieec adn teh cmuultaiv elegntho f lal hte rpevoiusp ieecs si nto mroe htant hed esriedv aleu spupleid yb teh appliactino.

update : 26-05-2017

ORA-24307 - invalid length for piece
ORA-24307 - invalid length for piece

  • ora-27143 : OS system call failure
  • ora-15177 : cannot operate on system aliases
  • ora-24382 : statement handled already executed or described
  • ora-24036 : invalid SORT_ORDER column string specified for queue table
  • ora-16119 : building transaction at SCN string
  • ora-33280 : (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.
  • ora-31151 : Cyclic definition encountered for string: "string"
  • ora-31486 : cannot support column string in this configuration
  • ora-00276 : CHANGE keyword specified but no change number given
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-31436 : duplicate change source string
  • ora-10388 : parallel query server interrupt (failure)
  • ora-40004 : penalty must be negative for BLAST-N
  • ora-01721 : USERENV(COMMITSCN) invoked more than once in a transaction
  • ora-27377 : windows cannot have event based schedules
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-28023 : must revoke grants of this role to other user(s) first
  • ora-23387 : replication parallel push dequeue error
  • ora-34061 : (MSEXECUT11) Session-only values cannot be added to non-unique concat dimension workspace object, or any of its base dimensions.
  • ora-16771 : failover to a physical standby database failed
  • ora-38497 : Expression Filter index does not exist
  • ora-31411 : change set string is referenced by a change table
  • ora-06593 : %s is not supported with natively compiled PL/SQL modules
  • ora-32808 : message system link string does not exist
  • ora-07860 : osnsoi: error setting up interrupt handler
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-38900 : missing mandatory column "string" of error log table "string"
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-16255 : Log Auto Delete conflicts with another LogMiner session
  • 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.