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

PCB-00701: MAX OCCURRANCES must be between 1 and 65535

1 Answers  

---

ORA-29843: indextype should support atleast one operator

1 Answers  

---

ORA-25138: %s initialization parameter has been made obsolete

1 Answers  

---

KUP-04059: found EOF in length portion of VARIABLE record in file string

1 Answers  

---

ORA-02272: constrained column cannot be of LONG datatype

1 Answers  

---

ORA-01921: role name 'string' conflicts with another user or role name

1 Answers  

---

ORA-02490: missing required file size in RESIZE clause

1 Answers  

---

ORA-16783: instance string not open for read and write access

1 Answers  

---

ORA-600?

1 Answers   IBM,

---

NID-00503: DBNAME New database name (NONE)

1 Answers  

---

ORA-23438: missing refresh group template

1 Answers  

---

ORA-12494: cannot insert or delete a level, category, or release category

1 Answers  

---