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 : 18-08-2017

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

  • ora-29507 : query derived from USING clause found zero or many rows
  • ora-36682 : (XSDPART20) Partition name string appears twice.
  • ora-23315 : repcatlog version or request string is not supported by version string
  • ora-16139 : media recovery required
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-03279 : invalid INSTANCE specified
  • ora-01248 : file string was created in the future of incomplete recovery
  • ora-16952 : Failed to bind this SQL statement.
  • ora-12424 : length exceeds binary label size
  • ora-13275 : spatial index creation failure on unsupported type
  • ora-19804 : cannot reclaim string bytes disk space from string limit
  • ora-13025 : polygon does not close
  • ora-02731 : osnrnf: malloc of buffer failed
  • ora-28333 : column is not encrypted
  • ora-01466 : unable to read data - table definition has changed
  • ora-16200 : Skip procedure requested to skip statement
  • ora-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-16545 : unable to get response
  • ora-22347 : No changes to type specified for ALTER TYPE
  • ora-06017 : NETASY: message receive failure
  • ora-07201 : slhom: oracle_home variable not set in environment.
  • ora-36735 : A value exceeded the MAX specification
  • ora-38787 : Creating the first guaranteed restore point requires mount mode when flashback database is off.
  • ora-02784 : Invalid shared memory ID specified
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-06753 : TLI Driver: name-to-address mapping failed
  • ora-03136 : inbound connection timed out
  • ora-02215 : duplicate tablespace name clause
  • ora-00384 : Insufficient memory to grow cache
  • ora-27004 : invalid blocksize specified
  • 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.