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
|Is This Answer Correct ?||0 Yes||0 No|
LPX-00004: internal error "~s"
ORA-24028: cannot create a reciever non-repudiable single consumer queue
EXP-00010: %s is not a valid username
ORA-06518: PL/SQL: Probe version string incompatible with version string
ORA-09291: sksachk: invalid device specified for archive destination
AUD-00704: invalid input format
RMAN-06493: only UNTIL TIME clause is allowed when performing a restore from autobackup, found: string
ORA-28506: parse error in data dictionary translation for string stored in string
ORA-06927: CMX: T_DATAIN received before all data written
ORA-28651: Primary index on IOTs can not be marked unusable
ORA-01230: cannot make read only - file string is offline
SQL*Loader-00932: Could not truncate table string.