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 : 30-04-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-09918 : Unable to get user privileges from SQL*Net
  • ora-32162 : Read/Write SQL method not registered
  • ora-19108 : WHITESPACE keyword expected
  • ora-37077 : (XSMCSESS05) Object workspace object is specified more than once.
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-31516 : CDC change set string already exists
  • ora-24431 : Statement does not exist in the cache
  • ora-12091 : cannot online redefine table "string"."string" with materialized views
  • ora-38763 : flashback not started; enabled threads have changed
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-00376 : file string cannot be read at this time
  • ora-15091 : operation incompatible with open handle in this session
  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-30478 : Specified dimension does not exist
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-16611 : operation aborted at user request
  • ora-19650 : Offline-range record recid string stamp string in file string has SCN string
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-02088 : distributed database option not installed
  • ora-12842 : Cursor invalidated during parallel execution
  • ora-22893 : constraint can be specified only for REF columns
  • ora-13625 : %s is an invalid advisor object type.
  • ora-01111 : name for data file string is unknown - rename to correct file
  • ora-06449 : The list IO or the sysvendor is not installed.
  • ora-29259 : end-of-input reached
  • ora-27455 : Only "SYS" is a valid schema for a string.
  • ora-25291 : Buffer does not exist for the specified queue
  • ora-31495 : error in synchronous change table on "string"."string"
  • ora-29250 : Invalid index specifed in call to dbms_sql.bind_array
  • ora-19760 : error starting change tracking
  • 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.