ORA-12602: TNS: Connection Pooling limit reached

Cause : Theo pertaionf ailde beacusem axiumm atcivec urrnet cnonecitonsh as eben erachde. I tmayn ot eb a eral rerorw hent he oCnnetcionP oolnig faetur eis neablde. I tis opssilbe taht teh aplpicaiton alterr eisuses hte oepratoin adn successufllyg rab sthec onncetio npoo lslo tandp roceeds.

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

Thi sis na inetrna lerrro. Eanblet racnig adn atetmptt o rpeeatt he reror .If ti ocucrs gaain ,conatct rOacl eCusotmerS upprot.

update : 25-04-2017
ORA-12602

ORA-12602 - TNS: Connection Pooling limit reached
ORA-12602 - TNS: Connection Pooling limit reached

  • ora-33452 : (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-02835 : Server unable to send signal to client
  • ora-02221 : invalid MAXEXTENTS storage option value
  • ora-36634 : (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.
  • ora-28111 : insufficient privilege to evaluate policy predicate
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-13453 : GeoRaster metadata layer error
  • ora-01022 : database operation not supported in this configuration
  • ora-29318 : datafile string is online
  • ora-01764 : new update value of join is not guaranteed to be unique
  • ora-31671 : Worker process string had an unhandled exception.
  • ora-13638 : The user interrupted the current operation.
  • ora-01463 : cannot modify column datatype with current constraint(s)
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-29970 : Specified registration id does not exist
  • ora-13154 : invalid precision specified
  • ora-12993 : tablespace 'string' is offline, cannot drop column
  • ora-19648 : datafile string: incremental-start SCN equals checkpoint SCN
  • ora-00104 : deadlock detected; all public servers blocked waiting for resources
  • ora-24852 : protocol error during statement execution
  • ora-02847 : Server did not terminate when posted
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-19320 : Host name not specified in HTTP URL
  • ora-31679 : Table data object string has long columns, and longs can not be loaded/unloaded using a network link
  • ora-19012 : Cannot convert XML fragment to the required datatype
  • 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.