NNC-00001 maximum number of connections already open
March 20th, 2009
Description:
NNC-00001 maximum number of connections already open
Cause:
All available name service connections are handling requests.
Categories
- Errors (22343)
- Java (777)
- JAVA-API (4)
- JAVA-Compiler (62)
- JAVA-DBUnit (7)
- JAVA-Demo (1)
- JAVA-EJB (193)
- JAVA-GlassFish (2)
- JAVA-Hibernate (45)
- JAVA-Installation (1)
- JAVA-JBoss (41)
- JAVA-JDBC (9)
- JAVA-Jetspeed (4)
- JAVA-Jetty (2)
- JAVA-JMF (6)
- JAVA-JNI (7)
- JAVA-JNLP (3)
- JAVA-JRE (111)
- JAVA-JSP (14)
- JAVA-JUnit (2)
- JAVA-JVM (39)
- JAVA-Language (1)
- JAVA-Mail (22)
- JAVA-Plug-in (1)
- JAVA-Servlets (6)
- JAVA-Tomcat (166)
- JAVA-Tools (28)
- MySql (422)
- MySql-Client (52)
- MySql-Server (370)
- Oracle (20434)
- Oracle DB (13621)
- ORA-00000 to ORA-00899 (338)
- ORA-00900 to ORA-01499 (511)
- ORA-01500 to ORA-02099 (548)
- ORA-02100 to ORA-04099 (645)
- ORA-04100 to ORA-07499 (551)
- ORA-07500 to ORA-09857 (521)
- ORA-09858 to ORA-12299 (219)
- ORA-12300 to ORA-12399 (23)
- ORA-12400 to ORA-12699 (86)
- ORA-12700 to ORA-19399 (1219)
- ORA-19400 to ORA-24279 (848)
- ORA-24280 to ORA-29249 (956)
- ORA-29250 to ORA-32799 (1049)
- ORA-32800 to ORA-32999 (42)
- ORA-33000 to ORA-65535 (143)
- ORADB-AMD (42)
- ORADB-AUD (13)
- ORADB-DBV (1)
- ORADB-DRG (658)
- ORADB-EPC (174)
- ORADB-EXP (98)
- ORADB-IMG (135)
- ORADB-IMP (96)
- ORADB-KUP (97)
- ORADB-LCD (23)
- ORADB-LFI (91)
- ORADB-LPX (155)
- ORADB-LRM (24)
- ORADB-LSX (127)
- ORADB-MOD (89)
- ORADB-NCR (71)
- ORADB-NID (39)
- ORADB-NMP (12)
- ORADB-NNC (44)
- ORADB-NNF (157)
- ORADB-NNL (423)
- ORADB-NNO (174)
- ORADB-NPL (29)
- ORADB-NZE (138)
- ORADB-O2F (41)
- ORADB-O2I (27)
- ORADB-O2U (13)
- ORADB-PCB (121)
- ORADB-PCC (357)
- ORADB-PLS (523)
- ORADB-QSM (245)
- ORADB-RMAN (772)
- ORADB-SQL (56)
- ORADB-TNS (850)
- ORADB-VID (7)
- Weblogic 10.3 (3521)
- WL103-Api (21)
- WL103-ApplicationPoller (10)
- WL103-Bridge (19)
- WL103-BugReporter (2)
- WL103-Cache (1)
- WL103-Cluster (51)
- WL103-ClusterExtension (4)
- WL103-Common (54)
- WL103-Config (28)
- WL103-Connector (235)
- WL103-ConsoleServices (3)
- WL103-CustomModule (1)
- WL103-DatabaseLessLeasing (1)
- WL103-DebugModule (2)
- WL103-DeployerRuntime (100)
- WL103-DeploymentManager (20)
- WL103-DeploymentService (24)
- WL103-Diagnostics (106)
- WL103-DiagnosticsHarvester (4)
- WL103-DiagnosticsInstrumentor (8)
- WL103-DiagnosticsWatch (1)
- WL103-DRS (2)
- WL103-EJB (378)
- WL103-Engine (22)
- WL103-Entitlement (1)
- WL103-FastSwap (1)
- WL103-HarvesterJMX (1)
- WL103-Health (6)
- WL103-HTTP (244)
- WL103-HTTPSession (55)
- WL103-IIOP (19)
- WL103-JDBC (70)
- WL103-JMS (81)
- WL103-JMSClientException (168)
- WL103-JMSException (79)
- WL103-JMX (6)
- WL103-JNDI (4)
- WL103-Kernel (5)
- WL103-LogMgmt (13)
- WL103-Management (150)
- WL103-MasterDeployer (8)
- WL103-MBeanTypingUtil (4)
- WL103-Messaging (6)
- WL103-MIException (32)
- WL103-Net (3)
- WL103-NodeManager (41)
- WL103-Path (4)
- WL103-PubSub (32)
- WL103-PubSubJms (6)
- WL103-RMI (12)
- WL103-SAF (7)
- WL103-Security (646)
- WL103-Server (15)
- WL103-Service (60)
- WL103-Singleton (1)
- WL103-SlaveDeployer (44)
- WL103-SNMP (47)
- WL103-Socket (22)
- WL103-SPIDeployer (88)
- WL103-Store (65)
- WL103-T3Misc (13)
- WL103-T3Srvr (68)
- WL103-TX (91)
- WL103-TXException (4)
- WL103-WebService (21)
- WL103-WLSConsole (3)
- WL103-WorkManager (6)
- WL103-WTC (154)
- WL103-XML (18)
- WebLogic 9.2 (3292)
- WL92-ApplicationPoller (10)
- WL92-Bridge (19)
- WL92-BugReporter (2)
- WL92-Cluster (50)
- WL92-Common (54)
- WL92-Config (28)
- WL92-Connector (236)
- WL92-ConsoleServices (3)
- WL92-CustomModule (1)
- WL92-DeployerRuntime (100)
- WL92-DeploymentManager (20)
- WL92-DeploymentService (24)
- WL92-Diagnostics (98)
- WL92-DRS (2)
- WL92-EJB (361)
- WL92-Entitlement (1)
- WL92-Health (5)
- WL92-HTTP (243)
- WL92-HTTPSession (52)
- WL92-IIOP (19)
- WL92-JDBC (68)
- WL92-JMS (82)
- WL92-JMSClientException (168)
- WL92-JMSException (79)
- WL92-JMX (6)
- WL92-JNDI (4)
- WL92-Kernel (5)
- WL92-LogMgmt (13)
- WL92-Management (148)
- WL92-MasterDeployer (8)
- WL92-Messaging (6)
- WL92-MIException (32)
- WL92-Net (3)
- WL92-NodeManager (40)
- WL92-Path (4)
- WL92-RMI (12)
- WL92-SAF (7)
- WL92-Security (646)
- WL92-Server (15)
- WL92-SlaveDeployer (44)
- WL92-SNMP (32)
- WL92-Socket (21)
- WL92-SPIDeployer (88)
- WL92-Store (64)
- WL92-T3Misc (13)
- WL92-T3Srvr (68)
- WL92-TX (90)
- WL92-TXException (2)
- WL92-WebService (21)
- WL92-WLSConsole (3)
- WL92-WorkManager (6)
- WL92-WTC (149)
- WL92-XML (17)
- Oracle DB (13621)
- Perl (710)
- Java (777)
If the problem occurs when running a name server, increase the values of NAMES.MAX_OPEN_CONNECTIONS. If the problem occurs in a client program, turn on tracing and re-execute the failing operation. If the error persists, contact Oracle Support Services.