Re: Cursor Cache and Excessive Parsing

Thanks for the feedback...

My shared pool is 100Mb..

It looks like I have been short sighted. I have assumed all along that most of the reparsing was down to soft rather that than hard parsing. But in fact there were over 3000 "misses in library cache during parse".

Therefore the cursor cache will never help...

Now for the interesting part:

Why am I getting so many hard parses..? Well it turns out that the BATCH job does repeated TRUNCATES on all of the tables. Since TRUNC is a DDL statement, all of the cursors are invalidated.

So I can only conclude that there is nothing I can do at the back end to improve the throughput of this process.

Thanks for your help anyway..

Matt Received on Thu Feb 26 2004 - 11:20:26 CST