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-06737: TLI Driver: connection failed

1 Answers  

---

ORA-02759: Not enough request descriptors available

1 Answers  

---

ORA-13383: inconsistent network metadata: string

1 Answers  

---

ORA-29321: too many datafiles added since the point-in-time

1 Answers  

---

ORA-25449: invalid variable name: string

1 Answers  

---

---

ORA-29398: invalid privilege name specified

1 Answers  

---

PLS-00407: '*' not allowed here; a list of columns is required

1 Answers  

---

NPL-00411: incoming ASN.1 NULL encoding has nonzero length of string

1 Answers  

---

ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table

1 Answers  

---

QSM-02176: MV with UNION ALL in a view is too complex

1 Answers  

---

ORA-27415: repeat interval must start with the FREQ= clause

1 Answers  

---

ORA-31667: parameter name can not be defaulted

1 Answers  

---