Answer / guest

Cause: A connection had to be routed through a local socket
rather than a dispatcher. When this occurs, shared servers
are less beneficial because the session that owns the socket
cannot relinquish the process until the socket is closed.
The most likely cause is that no dispatcher is configured
for protocol=tcp.

Action: To improve the scalability of your configuration,
configure a dispatcher for protocol=tcp. To route these
particular connections through a particular set of
dispatchers, you can specify presentation=kgas. However, if
you haven't done so, any protocol=tcp dispatcher will be used.

Please add more information about this Error

TNS-12628: TNS:no event callbacks

1 Answers  

---

NNF-04008: Error writing outputfile

1 Answers  

---

ORA-13835: invalid attribute name specified

1 Answers  

---

ORA-22801: invalid object row variable

1 Answers  

---

TNS-00033: INTCTL: internal NL error

1 Answers  

---

ORA-02446: CREATE TABLE ... AS SELECT failed - check constraint violated

1 Answers  

---

ORA-02177: Missing required group number

1 Answers  

---

RMAN-06741: database name is "string" and DBID is string

1 Answers  

---

ORA-29741: IMR active for some, but not all members of cluster

1 Answers  

---

DRG-52111: error in knowledge base cache

1 Answers  

---

EXP-00079: Data in table "string" is protected. Conventional path may only be exporting partial table.

1 Answers  

---

ORA-13241: specified dimensionality does not match that of the data

1 Answers  

---