ORA-21521: exceeded maximum number of connections in OCI (object mode only)

Cause : User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.

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

Close some of existing and unused connections before opening more connections.

update : 23-06-2017

ORA-21521 - exceeded maximum number of connections in OCI (object mode only)
ORA-21521 - exceeded maximum number of connections in OCI (object mode only)

  • ora-08467 : error converting Oracle number to string
  • ora-31511 : name exceeds maximum length of 30 characters
  • ora-13274 : operator invoked with non-compatible SRIDs
  • ora-00109 : invalid value for attribute string: string
  • ora-16955 : Unknown error during SQL analyze.
  • ora-23326 : object group "string"."string" is quiesced
  • ora-01718 : BY ACCESS | SESSION clause not allowed for NOAUDIT
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-02709 : osnpop: pipe creation failed
  • ora-30653 : reject limit reached
  • ora-16224 : Database Guard is enabled
  • ora-07238 : slemcl: close error.
  • ora-39067 : Unable to close the log file.
  • ora-30486 : invalid window aggregation group in the window specification
  • ora-40225 : model is currently in use by another process
  • ora-39209 : Parameter string requires privileges.
  • ora-00212 : block size string below minimum required size of string bytes
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-15198 : operation string is not yet available
  • ora-16520 : unable to allocate resource id
  • ora-22150 : variable-length array has not been initialized
  • ora-31014 : Attempted to delete the root container
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-01679 : database must be mounted EXCLUSIVE and not open to activate
  • ora-30730 : referential constraint not allowed on nested table column
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-30940 : Cannot resolve prefix 'string' for QName node 'string'
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-28176 : incorrect certificate version
  • 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.