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-24085: operation failed, queue string is invalid

1 Answers  

---

ORA-01034: ORACLE not available

1 Answers  

---

CLSS-03201: An attempt to begin a nested reconfiguration failed.

1 Answers  

---

ORA-16642: db_unique_name mismatch

1 Answers  

---

ORA-31046: Incorrect argument(s) specified in the operator

1 Answers  

---

ORA-12015: cannot create a fast refresh materialized view from a complex query

1 Answers  

---

ORA-00483: During shutdown a process abnormally terminated

1 Answers  

---

ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.

1 Answers  

---

ORA-19617: file string contains different resetlogs data

1 Answers  

---

ORA-31515: CDC change source string already exists

1 Answers  

---

ORA-12951: Attempt to change default permanent tablespace to temporary

1 Answers  

---

TNS-01180: Missing listener object string in Directory Server

1 Answers  

---