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

TNS-00021: INTCTL: missing INTERCHANGE_DATA in INTCHG.ORA

1 Answers  

---

ORA-07273: sppst: invalid semaphore id.

1 Answers  

---

NNL-01000: SERVER FAILURE responses received: number

1 Answers  

---

ORA-19604: conversation file naming phase is over

1 Answers  

---

ORA-06449: The list IO or the sysvendor is not installed.

1 Answers  

---

ORA-01234: cannot end backup of file string - file is in use or recovery

1 Answers  

---

LSX-00286: duplicate key "~S" for {"~S"}"~S"

1 Answers  

---

TNS-12616: TNS:no event signals

1 Answers  

---

ORA-16174: user requested thread/sequence termination of managed recovery

1 Answers  

---

SQL-02155: Date Time Interval only valid with Dynamic=ANSI

1 Answers  

---

ORA-22291: Open LOBs exist at transaction commit time

1 Answers  

---

RMAN-08031: released channel: string

1 Answers  

---