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 : 29-04-2017

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

  • ora-26696 : no streams data dictionary for object with number string and version number string from source database string
  • ora-07580 : spstp: $GETJPIW failure
  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-13870 : Database-wide SQL tracing is not enabled
  • ora-01866 : the datetime class is invalid
  • ora-31493 : could not prepare session for LogMiner session
  • ora-28026 : user with same external name already exists
  • ora-25501 : ALTER SYSTEM QUIESCE RESTRICTED command failed
  • ora-06933 : CMX: error during attach
  • ora-12707 : error while getting create database NLS parameter string
  • ora-02797 : No requests available
  • ora-02428 : could not add foreign key reference
  • ora-09874 : TASDEF_READ: read error, unable to read tasdef@.dbf file.
  • ora-29308 : view TS_PITR_CHECK failure
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-12996 : cannot drop system-generated virtual column
  • ora-24312 : illegal parameters specified for allocating user memory
  • ora-28010 : cannot expire external or global accounts
  • ora-14270 : table is not partitioned by Range or Hash or List method
  • ora-29927 : error in executing the ODCIStatsCollect / ODCIStatsDelete routine
  • ora-06030 : NETDNT: connect failed, unrecognized node name
  • ora-07487 : scg_init_lm: cannot create lock manager instance.
  • ora-02372 : data for row: string
  • ora-30051 : VERSIONS clause not allowed here
  • ora-29508 : query derived from USING clause did not select a value of type string
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-16109 : failed to apply log data from previous primary
  • ora-16201 : Skip procedure requested to apply statement
  • ora-01266 : Unable to create unique file name
  • 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.