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-28263: Insufficient memory in global context pool

1 Answers  

---

PCC-02336: host variable expression has invalid type

1 Answers  

---

ORA-16122: applying large dml transaction at SCN string

1 Answers  

---

ORA-09772: osnpmetbrkmsg: message from host had incorrect message type

1 Answers  

---

ORA-06250: NETNTT: cannot allocate send and receive buffers

1 Answers  

---

QSM-01024: materialized view, string, has unknown compile errors

1 Answers  

---

LRM-00119: unable to obtain a valid value for 'string'

1 Answers  

---

ORA-04078: OLD and NEW values cannot be identical

1 Answers  

---

PLS-01702: Illegal syntax in COMMIT WORK statement

1 Answers  

---

NNL-00294: No entries found

1 Answers  

---

NPL-00100: cannot initialize ASN.1 context

1 Answers  

---

PLS-00506: User Defined Constrained Subtypes are disallowed

1 Answers  

---