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-22880: invalid REF

1 Answers  

---

NZE-28846: No private key

1 Answers  

---

PLS-00594: the SELF parameter can be declared only as IN or as IN OUT

2 Answers  

---

TNS-01180: Missing listener object string in Directory Server

1 Answers  

---

ORA-29854: keyword BITMAP may not be used in creating domain indexes

1 Answers  

---

ORA-12699: Native service internal error

1 Answers  

---

ORA-17502: ksfdcre:string Failed to create file string

1 Answers  

---

SQL-02114: Invalid SQL Cursor usage: trying to CLOSE a CLOSEd cursor

1 Answers  

---

ORA-22631: attribute [string] is is not well-formed or does not match the type

1 Answers  

---

LSX-00116: mutually exclusive facets are not allowed

1 Answers  

---

TNS-12552: TNS:operation was interrupted

1 Answers  

---

ORA-02826: Illegal block size

1 Answers  

---