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-39088: file name cannot contain a path specification

1 Answers  

---

ORA-23458: inappropriate flavor string at string

1 Answers  

---

NNL-00039: no RRs

1 Answers  

---

ORA-15033: disk 'string' belongs to diskgroup "string"

1 Answers  

---

DRG-50932: parser preference initialization failed

1 Answers  

---

AMD-00145: error attaching Workspace "string" in mode "string"

1 Answers  

---

ORA-39501: failed to notify CRS of a Startup/Shutdown event [number] (ignored)

1 Answers  

---

DRG-11114: result table format is not correct for this operation

1 Answers  

---

ORA-02450: Invalid hash option - missing keyword IS

1 Answers  

---

ORA-30728: maximum number of columns exceeded

1 Answers  

---

ORA-16775: Target standby in switchover operation has missing redo logs.

1 Answers  

---

QSM-02055: mv references a packed object table or view

1 Answers  

---