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

ORA-13629: The task or object string is being used by another operation.

1 Answers  

---

DRG-10703: invalid framework object string

1 Answers  

---

SQL*Loader-00644: end of logical record found when reading length of varying length field

1 Answers  

---

ORA-01890: NLS error detected

2 Answers  

---

LSX-00235: invalid URI "~S"

1 Answers  

---

ORA-03293: Cluster to be truncated is a HASH CLUSTER

1 Answers  

---

NNL-00035: File string or nested IFILEs not found.

1 Answers  

---

ORA-02329: column of datatype string cannot be unique or a primary key

1 Answers  

---

ORA-30020: UNDO_MANAGEMENT=AUTO needs Compatibility string or greater

1 Answers  

---

ORA-01743: only pure functions can be indexed

1 Answers  

---

SQL*Loader-00459: error fetching numeric value for sequence on column (string)

1 Answers  

---

SQL*Loader-00267: Control file must be first data file.

1 Answers  

---