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-04-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-14296 : Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-39024 : wrong schema specified for job
  • ora-27460 : cannot execute disabled job "string.string"
  • ora-29879 : cannot create multiple domain indexes on a column list using same indextype
  • ora-12416 : policy string not found
  • ora-00026 : missing or invalid session ID
  • ora-06752 : TLI: error in signal setup
  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-02045 : too many local sessions participating in global transaction
  • ora-10373 : parallel query server kill event
  • ora-29975 : Cannot register a query in the middle of an active transaction
  • ora-26748 : The one-to-one transformation function string encountered the following error: string
  • ora-16768 : SQL Apply unexpectedly offline
  • ora-00204 : error in reading (block string, # blocks string) of control file
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-40202 : column string does not exist in the input table string
  • ora-12488 : maximum label does not dominate minimum label
  • ora-32629 : measure used for referencing cannot be updated
  • ora-19669 : proxy copy functions cannot be run on DISK channel
  • ora-23335 : priority group string already exists
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-25436 : invalid table alias: string
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-06145 : NETTCP: unable to start ORASRV: images not installed
  • ora-24075 : cannot specify agent with NULL address and non-NULL protocol
  • ora-25115 : duplicate BLOCK option specification
  • ora-16780 : a database has exhausted its archived redo log storage quota
  • 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.