Re: flush shared pool problem

Steve,

If you were not using bind variables then that could definitely cause your problem.
The database engine will first look through the shared pool to see if a sql statement already exists. If you have literals in all of your statements then
you will take a cpu hit each time, especially if the shared pool is large and
there are a number of statements in the shared pool.

Perform a select * from v$sqlarea to see the statements.

Use bind variables, but if you can't implement them immediately then decrease the size
of the shared pool, or flush periodically.

Hope this helps,

Phil Cook Received on Thu Mar 09 2000 - 17:35:55 CST