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-31901: the current operation was cancelled by the user

1 Answers  

---

ORA-13615: The task or object string is greater than the maximum allowable length of 30 characters.

1 Answers  

---

ORA-16084: an apply engine is already running

1 Answers  

---

ORA-27141: invalid process ID

1 Answers  

---

RMAN-06904: backup of log thread number seq number lowscn string was cancelled

1 Answers  

---

---

NNO-00602: warning: forwarder number has invalid address, forwarder ignored

1 Answers  

---

TNS-12598: TNS:banner registration failed

1 Answers  

---

ORA-30017: segment 'string' is not supported in string Undo Management mode

1 Answers  

---

DRG-12802: invalid type column: string

1 Answers  

---

PCC-01011: USAGE IS BINARY clause must be terminated by "." on same line

1 Answers  

---

LPX-00278: invalid ~s proxy "~s"

1 Answers  

---

RMAN-06447: changed proxy copy available

1 Answers  

---