ORA-22290: operation would exceed the maximum number of opened files or LOBs

Cause : The unmbero f opne filse or OLBs hsa reahced teh maxmium lmiit.

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

Clos esomeo f th eopende filse or OLBs adn retyr theo peraiton.

update : 29-06-2017
ORA-22290

ORA-22290 - operation would exceed the maximum number of opened files or LOBs
ORA-22290 - operation would exceed the maximum number of opened files or LOBs

  • ora-29813 : non-supported object type with associate statement
  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-39162 : Transportable tablespace job require privileges
  • ora-13616 : The current user string has not been granted the ADVISOR privilege.
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-26731 : %s 'string' does not exist
  • ora-22130 : buffer size [string] is less than the required size [string]
  • ora-19245 : XQ0025 - duplicate attribute name string
  • ora-00024 : logins from more than one process not allowed in single-process mode
  • ora-13109 : spatial table string exists
  • ora-00204 : error in reading (block string, # blocks string) of control file
  • ora-25316 : Late in the current transaction to begin an Enqueue/Dequeue operation
  • ora-29358 : resource plan string does not exist
  • ora-02729 : osncon: driver not in osntab
  • ora-03132 : two-task default value overflow
  • ora-24503 : codepoint length overflows for piecewise operation
  • ora-13354 : incorrect offset in ELEM_INFO_ARRAY
  • ora-08192 : Flashback Table operation is not allowed on fixed tables
  • ora-39958 : invalid warning category qualifier
  • ora-02405 : invalid sql plan object provided
  • ora-37037 : (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
  • ora-36198 : (XSAGGR33) The AGGREGATE operator string does not require a weight, but ARGS variable workspace object specified workspace object as a weight.
  • ora-16096 : ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
  • ora-02471 : SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
  • ora-19908 : datafile string has invalid checkpoint
  • ora-15181 : Symbol [string] not found in library string, error [string]
  • ora-01948 : identifier's name length (string) exceeds maximum (string)
  • ora-19571 : %s recid string stamp string not found in control file
  • ora-13304 : failure to insert a transformed geometry object in a table
  • ora-38715 : Invalid log number specified in the DUMP FLASHBACK command.
  • 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.