I've gotten this error when I had large deletes going on, which had a lot of cascading deletes, and I was using the generated Designer Table API, whose triggers used up a lot of PL/SQL table memory. So, if you've got something going on that would use up a lot of memory, you might get the same problem. 3113 appears to be a catch-all error, meaning that if they didn't bother to tell you specifically what went wrong, you get this error. Enjoy. :( I always cringe when I get it. - -- http://www.freelists.org/webpage/oracle-l