Answer / guest

Cause: The Connection Manager could not be started.

Action: Assure that the executable can be found in the
standard Oracle executable area. Check the configuration
file INTCHG.ORA for errors and confirm that no other process
is using the ADDRESS(es) for this Connection Manager as
specified in TNSNET.ORA. Tracing can also be turned on in
the Connection Manager and detailed information about the
reason for the error determined. Consult the MultiProtocol
Interchange Administrator's Guide and Chapter 2 of this
manual for how to turn on tracing.

Please add more information about this Error

ORA-00319: log string of thread string has incorrect log reset status

1 Answers  

---

ORA-08234: smsget: cannot get instance listener address

1 Answers  

---

ORA-38418: ADT associated with the attribute set string does not exist

1 Answers  

---

ORA-25409: failover happened during the network operation,cannot continue

1 Answers  

---

ORA-28519: no heterogeneous data dictionary translations available

1 Answers  

---

LPX-00232: invalid use of a parameter entity reference

1 Answers  

---

TNS-12615: TNS:preempt error

1 Answers  

---

DRG-50803: failed to define output

1 Answers  

---

ORA-32737: Hang analysis aborted due to failed memory allocation

1 Answers  

---

ORA-23303: application raised generic exception during deferred RPC

1 Answers  

---

ORA-29961: too many warnings occurred in the execution of ODCIIndex DDL routine

1 Answers  

---

ORA-16762: Invalid database state

1 Answers  

---