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

LSX-00300: group must have name or ref but not both

1 Answers  

---

ORA-15185: Could not close dynamic library string, error [string]

1 Answers  

---

ORA-30753: column or table string is substitutable

1 Answers  

---

ORA-00210: cannot open the specified controlfile

1 Answers  

---

DRG-12422: write to client failed

1 Answers  

---

NID-00333: Cannot read the header of the following datafiles:

1 Answers  

---

ORA-22131: hexadecimal string length is zero

1 Answers  

---

NNL-01010: Forwarding contexts allocated: number

1 Answers  

---

ORA-03248: Too much of segment creation activity during migration

1 Answers  

---

ORA-12981: cannot drop column from an object type table

1 Answers  

---

ORA-02095: specified initialization parameter cannot be modified

1 Answers  

---

ORA-30688: maximum program calling depth exceeded

1 Answers  

---