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-32586: multiple specification of a supplemental logging attribute

1 Answers  

---

ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.

1 Answers  

---

ORA-02443: Cannot drop constraint - nonexistent constraint

1 Answers  

---

IMG-00524: mismatched quotes

1 Answers  

---

ORA-28102: policy does not exist

1 Answers  

---

---

ORA-38498: invalid stored attribute for the index object : string

1 Answers  

---

RMAN-06607: RMAN configuration parameters are:

1 Answers  

---

LSX-00333: literal "~S" is not valid with respect to the pattern

1 Answers  

---

ORA-07470: snclget: cannot get cluster number.

1 Answers  

---

ORA-12721: operation cannot execute when other sessions are active

1 Answers  

---

ORA-23342: invalid parameter column string

1 Answers  

---

DRG-12228: maximum number of field sections (string) exceeded

1 Answers  

---