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-28040: No matching authentication protocol

1 Answers  

---

ORA-12495: cannot disable an enabled level, category, or release category

1 Answers  

---

ORA-02774: Invalid request list latch time out value

1 Answers  

---

CLSR-06502: Failed to connect to database

1 Answers  

---

ORA-13368: simple polygon type has more than one exterior ring

1 Answers  

---

ORA-16074: ARCH processes must be active

1 Answers  

---

PCC-00009: Invalid host variable at column number in line number of file string

1 Answers  

---

ORA-01139: RESETLOGS option only valid after an incomplete database recovery

1 Answers  

---

ORA-22833: Must cast a transient type to a persistent type

1 Answers  

---

ORA-27059: could not reduce file size

1 Answers  

---

RMAN-06159: error while looking up backup set

1 Answers  

---

ORA-14629: cannot drop the only subpartition of a partition

1 Answers  

---