ORA-24401: cannot open further connections

Cause : uSffcieitnn mueb rfoc noentcoisna ern top erestni nht eoplot oxecetu eht eacll .oNn wec noentcoisnc nab eponedea sht eocnnaM xaparemet rusppildei nCOCInoentcoiPnooClerta eah sebner aehcde.

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

aCllO ICoCnnceitnooPlorCaeeti nCO_IPCOO_LERNITIAIILEZm do ena dnircaeest ehv laeuo fht eocnnaM xaparemet.r

update : 26-04-2017
ORA-24401

ORA-24401 - cannot open further connections
ORA-24401 - cannot open further connections

  • ora-25216 : invalid recipient, either NAME or ADDRESS must be specified
  • ora-30064 : Test support for two phase read only optimization
  • ora-29293 : A stream error occurred during compression or uncompression.
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-06503 : PL/SQL: Function returned without value
  • ora-30437 : all job queue processes have stopped running
  • ora-13505 : SYSAUX tablespace can not be made read only
  • ora-38955 : Source platform string not cross platform compliant
  • ora-26753 : Mismatched columns found in 'string.string'
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-38854 : cannot mark instance string (redo thread string) as disabled
  • ora-07510 : scgbrm: $getlki unexpected return on lockid string
  • ora-13441 : GeoRaster metadata SRS error
  • ora-40106 : positive target value not specified for computing Lift
  • ora-24432 : The statement that was returned is not tagged.
  • ora-33460 : (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • ora-02214 : duplicate BACKUP option specification
  • ora-37036 : (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-01179 : file string does not exist
  • ora-40301 : invalid cost matrix specification
  • ora-13417 : null or invalid layerNumber parameter
  • ora-22283 : filename contains characters that refer to parent directory
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-28111 : insufficient privilege to evaluate policy predicate
  • 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.