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-22618: attribute is a BAD NULL in the image handle

1 Answers  

---

ORA-24019: identifier for string too long, should not be greater than string characters

1 Answers  

---

ORA-00438: %s Option not installed

1 Answers  

---

ORA-02381: cannot drop PUBLIC_DEFAULT profile

1 Answers  

---

IMP-00074: The constraints flagged by ALL_CONSTRAINTS.BAD will break in 2000 A.D.

1 Answers  

---

ORA-30649: missing DIRECTORY keyword

1 Answers  

---

ORA-03296: cannot resize datafile - file string not found

1 Answers  

---

KUP-04065: error processing LOBFILE for field string

1 Answers  

---

ORA-24785: Cannot resume a non-migratable transaction

1 Answers  

---

TNS-00036: INTCTL: error reading from Navigator or Connection Manager error files

1 Answers  

---

ORA-22884: object modification failed

1 Answers  

---

ORA-32313: REFRESH FAST of "string"."string" unsupported after PMOPs

1 Answers  

---