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-19562: file string is empty

1 Answers  

---

PCC-00082: Length and scale specifications must be an integer

1 Answers  

---

ORA-04047: object specified is incompatible with the flag specified

1 Answers  

---

NZE-29224: Cannot locate matching certificate request.

1 Answers  

---

ORA-07713: sksamtd: could not mount archival device (SYS$MOUNT failure)

1 Answers  

---

---

NNL-00410: Average response time: string

1 Answers  

---

ORA-16619: Health Check timed out

1 Answers  

---

PCB-00629: Host variable is not of Internal LOB type

1 Answers  

---

NNL-00580: register_ns: <name server> <address> <domain>

1 Answers  

---

LPX-00234: namespace prefix "~S" is not declared

2 Answers  

---

ORA-01146: cannot start online backup - file string is already in backup

1 Answers  

---

ORA-28150: proxy not authorized to connect as client

1 Answers  

---