Ron, You can set cursor_sharing = force in the session or through a logon trigger. You should be able to identify this job by the machine it's coming from. That would be less impactive as some releases have issues with this and I didn't see what release you're on. Also, if you're still flushing the shared pool you might consider pining all your sequences beforehand so there's no unnecessary gaps. Larry -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Terry Sutton Sent: Tuesday, September 28, 2004 3:45 PM To: oracle-l@xxxxxxxxxxxxx Subject: Re: Shared Pool Tuning Have you tried cursor_sharing = force? --Terry ********************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. -- //www.freelists.org/webpage/oracle-l