ORA-22921: length of input buffer is smaller than amount requested

Cause : The buffer length is not big enough to hold the amount of data requested.

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

Verify that the number of bytes/characters specified in the input amount parameter is not bigger than the number of bytes specified in the input buffer length parameter. Allocate more space for the input buffer if necessary.

update : 24-05-2017

ORA-22921 - length of input buffer is smaller than amount requested
ORA-22921 - length of input buffer is smaller than amount requested

  • ora-13365 : layer SRID does not match geometry SRID
  • ora-31621 : error creating master process
  • ora-29252 : collection does not contain elements at index locations in call to dbms_sql.bind_array
  • ora-06772 : TLI Driver: error sending command
  • ora-02420 : missing schema authorization clause
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-24437 : OCIStmtExecute called before OCIStmtPrepare2.
  • ora-29520 : name string resolved to a class in schema string that could not be accessed
  • ora-12157 : TNS:internal network communication error
  • ora-39128 : unexpected DbmsJava error number from statement string
  • ora-16756 : resource guard could not open standby database read-only
  • ora-21614 : constraint violation for attribute number [string]
  • ora-29932 : the type being dropped is a statistics type
  • ora-01743 : only pure functions can be indexed
  • ora-12725 : unmatched parentheses in regular expression
  • ora-06432 : ssaio: Buffer Not Aligned
  • ora-08275 : Environment variable unset
  • ora-12532 : TNS:invalid argument
  • ora-07253 : spdes: semctl error, unable to destroy semaphore set.
  • ora-16809 : multiple warnings detected for the database
  • ora-38798 : Cannot perform partial database recovery
  • ora-12667 : Shared server: outbound transport protocol different from inbound
  • ora-12984 : cannot drop partitioning column
  • ora-16258 : marking index unusable due to a constraint violation
  • ora-16783 : instance string not open for read and write access
  • ora-34722 : (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
  • ora-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • ora-12585 : TNS:data truncation
  • ora-13381 : table:string not found in network:string
  • ora-16122 : applying large dml transaction at SCN 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.