ORA-30686: no dispatcher accepted TCP/IP connection request
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
Is This Answer Correct ? | 0 Yes | 0 No |
SQL*Loader-00600: Bind size of number bytes increased to number bytes to hold 1 row.
PLS-00145: duplicate external WITH CONTEXT specification in subprogram expression
ORA-07656: slsprom:$GETDVI failure
ORA-22893: constraint can be specified only for REF columns
DRG-11221: Third-party filter indicates this document is corrupted.
ORA-31011: XML parsing failed
ORA-03297: file contains used data beyond requested RESIZE value
ORA-19762: invalid file type string
ORA-19503: cannot obtain information on device, name="string", type="string", parms="string"
IMG-02001: 2FF01 - incorrect image format
PCC-01000: You are not authorized to run Pro*COBOL
ORA-36652: (XSDUNION11) workspace object is not a string type dimension.