Answer / guest

Cause: PL/SQL was designed primarily for robust transaction
processing. One consequence of the special-purpose design is
that the PL/SQL compiler imposes a limit on block size. The
limit depends on the mix of statements in the PL/SQL block.
Blocks that exceed the limit cause this error.

Action: The best solution is to modularize the program by
defining subprograms, which can be stored in an Oracle
database. Another solution is to break the program into two
sub-blocks. Have the first block INSERT any data the second
block needs into a temporary database table. Then, have the
second block SELECT the data from the table.

Please add more information about this Error

RMAN-06554: WARNING: file string is in backup mode

1 Answers  

---

NZE-28866: Invalid peer certificate encoding

1 Answers  

---

ORA-06957: No SID is currently available

1 Answers  

---

PCB-00315: DECLARE TABLE is an Oracle extension

1 Answers  

---

KUP-03013: OCI error getting database column scale.

1 Answers  

---

ORA-02256: number of referencing columns must match referenced columns

1 Answers  

---

PCC-02401: Host variable arrays of this type are currently not supported

1 Answers  

---

ORA-12538: TNS:no such protocol adapter

1 Answers  

---

PLS-00407: '*' not allowed here; a list of columns is required

1 Answers  

---

ORA-30341: dropped level has references

1 Answers  

---

PLS-01502: Constraint name and constraint status are non-ANSI.

1 Answers  

---

ORA-19816: WARNING: Files may exist in string that are not known to database.

1 Answers  

---