Answer / guest

Cause: At run time, the body of a program unit could not be
found. This can happen for one of two reasons. -- First,
there may be a unit 'a' which calls a module 'b', where the
spec for 'b' exists but not the body. In this case, since
the spec is present, there will be no compile-time errors.
-- Secondly, this can occur if there is a reference to a
sequence outside of the proper context such as a SQL
statement. In this case, the "spec" of the sequence
reference can be found, but it is invalid to actually run
code which references the sequence outside a SQL statement,
as in: i := seq.nextval;

Action: If caused by the first reason, create a body for the
object that is being referenced. If caused by the second
reason, move the sequence into a SQL statement. For example,
i := seq.nextval; can be replaced by: select seq.nextval
into temp from dual; i := temp;

Please add more information about this Error

EXP-00025: dictionary shows no column for constraint string.number

1 Answers  

---

ORA-24196: access the message in a wrong access mode

1 Answers  

---

PCC-00091: TYPE statement requires format specification for this Oracle datatype

1 Answers  

---

ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.

1 Answers  

---

CLSR-00531: Can not get primary group name

1 Answers  

---

ORA-00204: error in reading (block string, # blocks string) of controlfile

1 Answers  

---

ORA-39049: invalid parameter name string

1 Answers  

---

TNS-03503: Could not initialize NL

1 Answers  

---

QSM-01061: illegal query expression

1 Answers  

---

LSX-00240: bad float "~S"

1 Answers  

---

ORA-13269: internal error [string] encountered when processing geometry table

1 Answers  

---

RMAN-08523: restoring datafile string to string

1 Answers  

---