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-30036: unable to extend segment by string in undo tablespace 'string'

1 Answers  

---

RMAN-06169: could not read file header for datafile string error reason string

1 Answers  

---

IMP-00011: formatted table data not currently supported

1 Answers  

---

ORA-07802: slbtpd: overflow while converting to packed decimal

1 Answers  

---

PLS-00626: partitioned/clustered/ordered parameter must be a function argument

1 Answers  

---

IMG-00607: unable to write to destination image

1 Answers  

---

NNL-01067: Trace level: number

1 Answers  

---

ORA-12642: No session key

1 Answers  

---

PCC-00141: Thread Safety is not implemented in this precompiler

1 Answers  

---

ORA-39044: Metadata transform string has already been specified.

1 Answers  

---

PLS-00414: no column 'string' in table

1 Answers  

---

EXP-00018: datatype (number) for column string, table string.string is not supported

1 Answers  

---