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

QSM-00767: a SQL cache is not available to user string

1 Answers  

---

ORA-32803: value for string cannot be altered

1 Answers  

---

ORA-31465: cannot obtain a lock on the subscription

1 Answers  

---

DRG-12230: special section name must be one of string

1 Answers  

---

LSX-00136: "maxOccurs" is less than "minOccurs"

1 Answers  

---

---

NNL-00248: General request processing is now disabled

1 Answers  

---

ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition

1 Answers  

---

ORA-22900: the SELECT list item of THE subquery is not a collection type

1 Answers  

---

PCC-00044: Array size mismatch in INTO/USING. Minimum is: string(number:number)

1 Answers  

---

ORA-02805: Unable to set handler for SIGTPA

1 Answers  

---

PROT-00707: Cluster registry integrity check failed

1 Answers  

---

ORA-12713: Character data loss in NCHAR/CHAR conversion

1 Answers  

---