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

TNS-00019: INTCTL: error initializing the national language interface

1 Answers  

---

SQL*Loader-00508: record formating error in data file string

1 Answers  

---

ORA-02340: invalid column specification

1 Answers  

---

ORA-29859: error occurred in the execution of ODCIINDEXTRUNCATE routine

1 Answers  

---

ORA-19692: missing creation stamp on piece string

1 Answers  

---

---

ORA-07685: sou2os: supervisor stack set error

1 Answers  

---

RMAN-08125: keep attributes for the proxy copy are deleted

1 Answers  

---

ORA-19677: RMAN configuration name exceeds maximum length of string

1 Answers  

---

RMAN-10037: RPC anomaly detected on channel string, upinblt=number

1 Answers  

---

NNL-00954: Hash tables created: number

1 Answers  

---

ORA-09705: spcre: cannot initialize latch semaphore

1 Answers  

---

ORA-00339: archived log does not contain any redo

1 Answers  

---