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-14405: partitioned index contains partitions in a different tablespace

1 Answers  

---

ORA-39114: Dump files are not supported for string jobs

1 Answers  

---

NNO-00809: Unknown OCI error: number

1 Answers  

---

NNC-00004: connection is broken

1 Answers  

---

ORA-13441: GeoRaster metadata SRS error

1 Answers  

---

ORA-12901: default temporary tablespace must be of TEMPORARY type

1 Answers  

---

ORA-08207: ora_addr: cannot open address file

1 Answers  

---

NZE-29032: The given identity is not complete.

1 Answers  

---

ORA-27010: skgfwrt: write to file failed

1 Answers  

---

QSM-02063: aggregate function in mv

1 Answers  

---

KUP-03004: absolute end (number) specified with relative start (number) for field string

1 Answers  

---

SQL*Loader-00471: OID or SID clause has an argument that is CONSTANT

1 Answers  

---