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-31212: DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.

1 Answers  

---

PROC-00009: Cannot perform cluster registry operation because the buffer passed is too small.

1 Answers  

---

SQL*Loader-00958: Error popping data relocation address stack

1 Answers  

---

ORA-07487: scg_init_lm: cannot create lock manager instance.

1 Answers  

---

ORA-30657: operation not supported on external organized table

2 Answers  

---

ORA-00266: name of archived log file needed

1 Answers  

---

ORA-13449: GeoRaster metadata ULTCoordinate error

1 Answers  

---

ORA-32742: Hang analysis initialize failed

1 Answers  

---

ORA-08443: syntax error in BLANK WHEN ZERO clause in mask options

1 Answers  

---

ORA-16204: DDL successfully applied

1 Answers  

---

NZE-29238: the cryptographic engine could not apply the algorithm

1 Answers  

---

ORA-15127: ASM file name 'string' cannot use templates

1 Answers  

---