Answer / guest

Cause: The declaration of a subprogram or cursor name is
ambiguous because there was no exact match between the
declaration and the call and more than one declaration
matched the call when implicit conversions of the parameter
datatypes were used. The subprogram or cursor name might be
misspelled, its declaration might be faulty, or the
declaration might be placed incorrectly in the block structure.

Action: Check the spelling and declaration of the subprogram
or cursor name. Also confirm that its call is correct, its
parameters are of the right datatype, and, if it is not a
built-in function, that its declaration is placed correctly
in the block structure.

Please add more information about this Error

ORA-39095: Dump file space has been exhausted: Unable to allocate string bytes

1 Answers  

---

PLS-00635: method does not override

1 Answers  

---

ORA-06537: OUT bind variable bound to an IN position

1 Answers  

---

LPX-00014: context is not clean

1 Answers  

---

O2F-00312: Illegal or missing type version string

1 Answers  

---

ORA-23431: wrong state: string

1 Answers  

---

ORA-32034: unsupported use of WITH clause

1 Answers  

---

ORA-00298: Missing or invalid attribute value

1 Answers  

---

TNS-04046: Invalid specification for source

1 Answers  

---

ORA-00287: specified change number string not found in thread string

1 Answers  

---

ORA-25008: no implicit conversion to LOB datatype in instead-of trigger

1 Answers  

---

ORA-30160: Unable to access the file

1 Answers  

---