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-01003: no query rewrite on DDL queries

1 Answers  

---

SQL*Loader-00801: all INTO TABLE clauses must have the same options (string)

1 Answers  

---

ORA-13231: failed to create index table [string] during R-tree creation

1 Answers  

---

ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object

1 Answers  

---

PLS-00305: previous use of 'string' (at line string) conflicts with this use

1 Answers  

---

ORA-13502: Cannot rename SYSAUX tablespace

1 Answers  

---

ORA-21601: attribute is not an object

1 Answers  

---

IMG-00581: output format does not support the specified contentFormat

1 Answers  

---

NCR-01005: NCRS: Failed to flush the output buffer.

1 Answers  

---

ORA-30122: value 'string' for 'string' must be between 'number' and 'number'

1 Answers  

---

ORA-28523: ORACLE and heterogeneous agent are incompatible versions

1 Answers  

---

AUD-00702: unable to initialize audio processing environment

1 Answers  

---