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 : 22-08-2017

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

  • ora-02383 : illegal cost factor
  • ora-19025 : EXTRACTVALUE returns value of only one node
  • ora-28270 : Malformed user nickname for password authenticated global user.
  • ora-14168 : only one subpartition may be modified
  • ora-07631 : smcacx: $EXPREG failure
  • ora-02457 : The HASH IS option must specify a valid column
  • ora-30383 : specified dimension level does not exist in the attribute
  • ora-02789 : Maximum number of files reached
  • ora-33261 : (DBERRLEN) Analytic workspace string extension number truncated at number bytes while trying to read at number.
  • ora-16123 : transaction string string string is waiting for commit approval
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-13036 : Operation [string] not supported for Point Data
  • ora-14051 : invalid ALTER MATERIALIZED VIEW option
  • ora-27015 : skgfcls: failed to close the file
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-02286 : no options specified for ALTER SEQUENCE
  • ora-07620 : smscre: illegal database block size
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-39033 : Data cannot be filtered under the direct path access method.
  • ora-07220 : slspool: wait error.
  • ora-29385 : cannot create plan directive from string to string
  • ora-13213 : failed to generate spatial index for window object
  • ora-28272 : Domain policy restricts password based GLOBAL user authentication.
  • ora-28504 : ROWID not found in ROWID cache for heterogeneous database link
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-24281 : invalid access past the maximum size of LOB parameter string
  • ora-31605 : the following was returned from string in routine string: LPX-number: 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.