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

ORA-13643: The task can not be interrupted or cancelled.

1 Answers  

---

ORA-07702: unrecognized device type in archive text

1 Answers  

---

TNS-12601: TNS:information flags check failed

1 Answers  

---

NZE-28769: Specified method does not exist.

1 Answers  

---

TNS-01002: stop [<listener_name>] : stop listener

1 Answers  

---

---

ORA-13228: spatial index create failed due to invalid type

1 Answers  

---

ORA-07610: $GETJPIW failed in retrieving the user's MAC priviledges

1 Answers  

---

IMP-00011: formatted table data not currently supported

1 Answers  

---

ORA-12468: max write level does not equal max read level

1 Answers  

---

UDI-00011: parameter string is incompatible with parameter string

1 Answers  

---

ORA-30766: cannot modify scope for a REF column with a REFERENCES constraint

1 Answers  

---

PCC-02133: CMD-LINE: Error in string processing function

1 Answers  

---