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-13264: geometry identifier column string does not exist in table string

1 Answers  

---

NNO-00055: invalid domain minimum TTL "string"

1 Answers  

---

ORA-14287: cannot REBUILD a partition of a Composite Range partitioned index

1 Answers  

---

NNL-00515: Deletes a name and its data

1 Answers  

---

ORA-13403: invalid rasterDataTable specification

1 Answers  

---

ORA-06579: Bind variable not big enough to hold the output value

1 Answers  

---

RMAN-06475: parallelism setting out of range (1-254): number

1 Answers  

---

ORA-29360: retry operation. Too much concurrent activity

1 Answers  

---

RMAN-06133: recovery catalog may have obsolete data for datafile string

1 Answers  

---

NZE-29158: Unable to open library.

1 Answers  

---

ORA-22292: Cannot open a LOB in read-write mode without a transaction

1 Answers  

---

ORA-24326: handle passed in is already initialized

1 Answers  

---