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;


Relared Errors:
PLS-00901: the
data type of column `string` of table `string` is not
support

PLS-00902: A
READ-ONLY bind variable used in OUT or IN-OUT context

PLS-00904:
insufficient privilege to access object string

PLS-00905:
object string is invalid

PLS-00906:
Compilation is not possible

PLS-00907:
cannot load library unit string (referenced by
string)

PLS-00908: The
stored format of string is not supported by this
release

PLS-00909:
object string is not declared or insufficient privileges to access
object

PLS-00910:
insufficient privilege to inherit from type string

PLS-00920:
parameter plsql_native_library_dir is not set