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-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set

1 Answers  

---

ORA-01574: maximum number of concurrent transactions exceeded

1 Answers  

---

ORA-00322: log string of thread string is not current copy

1 Answers   Sabro,

---

ORA-32775: cannot change size attributes of read only tablespace string

1 Answers  

---

DRG-11209: filename for string exceeds maximum length of string

1 Answers  

---

ORA-09951: Unable to create file

1 Answers  

---

ORA-24273: translation text is required if translation type is T or S

1 Answers  

---

ORA-39043: Object type string is not supported for string jobs.

1 Answers  

---

ORA-14522: Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]

1 Answers  

---

ORA-28611: bitmap index is corrupted - see trace file for diagnostics

1 Answers  

---

QSM-02019: mv references another mv in FROM clause

1 Answers  

---

ORA-29508: query derived from USING clause did not select a value of type string

1 Answers  

---