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

CLSR-06506: Error number encountered when executing string

1 Answers  

---

ORA-32034: unsupported use of WITH clause

1 Answers  

---

TNS-12633: No shared authentication services

1 Answers  

---

KUP-04004: error while reading file string

1 Answers  

---

ORA-04073: column list not valid for this trigger type

1 Answers  

---

ORA-16750: Resource guard encountered errors while activating logical primary

1 Answers  

---

NID-00373: Revert changes for database string (Y/[N]) =>

1 Answers  

---

ORA-13233: failed to create sequence number [string] for R-tree

1 Answers  

---

NID-00131: Control file is not current

1 Answers  

---

ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.

1 Answers  

---

ORA-01657: invalid SHRINK option value

1 Answers  

---

ORA-01664: Transaction which has expanded the Sort Segment has aborted

1 Answers  

---