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

ORA-12839: cannot modify an object in parallel after modifying it

1 Answers  

---

QSM-02021: set operator encountered in mv

1 Answers  

---

ORA-08002: sequence string.CURRVAL is not yet defined in this session

1 Answers  

---

ORA-14028: missing AT or VALUES keyword

1 Answers  

---

ORA-07441: function address must be aligned on string byte boundary

1 Answers  

---

ORA-29801: missing RETURN keyword

1 Answers  

---

ORA-28666: option not allowed for an index on UROWID column(s)

1 Answers  

---

ORA-23452: flavor string of object group "string"."string" is already published

1 Answers  

---

ORA-16027: parameter string is missing a destination option

1 Answers  

---

ORA-01598: rollback segment 'string' is not online

1 Answers  

---

NNL-00932: Requests refused, type syntax mismatch: number

1 Answers  

---

ORA-14082: new partition name must differ from that of any other partition of the object

1 Answers  

---