Originally posted by seanryan
I monitored a large insert job which appeared to be using 80n megs of shared pool every hour of execution and just today moved this to a standalone database for processing.
What kind of insert job could be using 80 megs of shared pool? What is it using such amount of shared pool for? Do you extensively use PL/SQL tables during that insert job?

It simply doesn't make to much sence to me, can you describe n more detail what this insert job is doing?