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

QSM-01036: unmatched column, string, present in query after view merging

1 Answers  

---

ORA-30393: a query block in the statement did not rewrite

1 Answers  

---

NNL-00835: Average delete processing time: string

1 Answers  

---

ORA-16584: illegal operation on a standby site

1 Answers  

---

LPX-00280: HTTP error ~s

1 Answers  

---

ORA-39077: unable to subscribe agent string to queue "string"

1 Answers  

---

TNS-00237: Failed to refuse connection

1 Answers  

---

EXP-00070: attempt to free unallocated memory

1 Answers  

---

ORA-02380: profile string does not exist

1 Answers  

---

ORA-00326: log begins at change string, need earlier change string

1 Answers  

---

PCC-01012: DATA DIVISION not found

1 Answers  

---

RMAN-03017: recursion detected in stored script string

1 Answers  

---