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-21609: memory being resized without being allocated first

1 Answers  

---

ORA-13437: GeoRaster metadata blocking error

1 Answers  

---

ORA-08449: invalid numeric symbol found in picture mask

1 Answers  

---

ORA-25147: UNIFORM SIZE value greater than maximum extent size

1 Answers  

---

how to resolve the sqlcode -501 erroe in db2?

2 Answers   Syntel,

---

PCC-02388: Arrays not allowed in FROM/WHERE clause of SELECT statement

1 Answers  

---

ORA-38311: cannot purge objects owned by other users

1 Answers  

---

TNS-00535: Failed to send or receive disconnect message

1 Answers  

---

ORA-13145: failed to generate range list

1 Answers  

---

NZE-28791: certificate verification failure

1 Answers  

---

ORA-08444: syntax error in JUSTIFIED clause in mask options

1 Answers  

---

ORA-00037: cannot switch to a session belonging to a different server group

1 Answers  

---