ORA-22280: no more buffers available for operation

Cause : There are two causes: (1) All buffers in the buffer pool have been used up by previous operations (2) Attempt to flush a LOB without any previous buffered update operations.

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

For (1), flush the LOB(s) through the locator that is being used to update the LOB. For (2), write to the LOB through a locator enabled for buffering before attempting to flush buffers.

update : 24-06-2017

ORA-22280 - no more buffers available for operation
ORA-22280 - no more buffers available for operation

  • ora-12732 : invalid interval value in regular expression
  • ora-22883 : object deletion failed
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-27543 : Failed to cancel outstanding IPC request
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-32615 : incorrect use of MODEL IS ANY predicate
  • ora-06733 : TLI Driver: failed to receive disconnect
  • ora-30018 : Create Rollback Segment failed, USN string is out of range
  • ora-02054 : transaction string in-doubt
  • ora-04064 : not executed, invalidated string
  • ora-13353 : ELEM_INFO_ARRAY not grouped in threes
  • ora-16537 : child count exceeded
  • ora-09829 : pw_createPorts: server call pws_start_instance failed.
  • ora-09266 : spawn: error starting an Oracle process
  • ora-19805 : recid string of string was deleted to reclaim disk space
  • ora-29760 : instance_number parameter not specified
  • ora-39309 : schema sync operation failed
  • ora-07427 : spstp: cannot change directory to dbs.
  • ora-28560 : error in configuration of agent process
  • ora-24367 : user handle has not been set in service handle
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-28341 : cannot encrypt constraint column(s) with salt
  • ora-08458 : invalid format parameter
  • ora-01254 : cannot end online backup - file string in recovery manager backup
  • ora-32766 : instr with negative offset: use varchar semantics on LOBs
  • ora-16214 : apply stalled for apply delay
  • ora-22064 : invalid NLS parameter string [string]
  • ora-01632 : max # extents (string) reached in index string.string
  • ora-31687 : error creating worker process string with worker id 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.