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-19750: change tracking file: 'string'

1 Answers  

---

ORA-01062: unable to allocate memory for define buffer

1 Answers  

---

ORA-25221: enqueue failed, signature specified queue not supporting non-repudiation

1 Answers  

---

ORA-12668: Dedicated server: outbound protocol does not support proxies

1 Answers  

---

ORA-01309: invalid session

1 Answers  

---

AMD-00143: View name "string" must be fully qualified with the Owner.

1 Answers  

---

KUP-00554: error encountered while parsing access parameters

1 Answers  

---

ORA-24414: Only number sessions could be started.

1 Answers  

---

ORA-01301: error writing to file during flat file build

1 Answers  

---

ORA-27073: Trying to close a file which has async I/Os pending to be dequeued

1 Answers  

---

NZE-28776: Output buffer supplied is too small.

1 Answers  

---

ORA-30107: parameter name abbreviation 'string' is not unique

1 Answers  

---