Interested to Buy Any Domain ? << Click Here >> for more details...
TNS-12602: TNS: Connection Pooling limit reached
- 1 Answers
- 4203 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The operation failed because maximum active current
connections has been reached. It may not be a real error
when the Connection Pooling feature is enabled. It is
possible that the application later reissues the operation
and successfully grabs the connection pool slot and proceeds.
Action: This is an internal error. Enable tracing and
attempt to repeat the error. If it occurs again, contact
Oracle Customer Support.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-22608: cannot add an attribute to the already generated image handle
TNS-12224: TNS:no listener
ORA-01618: redo thread string is not enabled - cannot mount
ORA-02275: such a referential constraint already exists in the table
ORA-28004: invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
ORA-29746: Cluster Synchronization Service is being shut down.
ORA-01681: max # extents (string) reached in LOB segment in tablespace string
ORA-02086: database (link) name is too long
ORA-29351: can not transport system, sysaux, or temporary tablespace 'string'
ORA-38759: Database must be mounted EXCLUSIVE and not open.
ORA-32637: Self cyclic rule in sequential order MODEL
PCC-02341: host variable has illegal type
Oracle Errors 
