Rick I think this is an issue that all of us struggle with from time to time. I think you've received some excellent discussion of your issues. I just wanted to congratulate you for having 3 environments (development, QA, production). At least it sounds from your posting that you are finding most of the problems before they surprise you in production. We are just implementing the 3 environment model and it is encouraging to see your success in this arena, even if it isn't curing all the ills. But I suppose if there weren't a few problems, I wouldn't be needed. Dennis Williams DBA Lifetouch, Inc. dwilliams@xxxxxxxxxxxxx -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Rick Stephenson Sent: Monday, June 07, 2004 2:36 PM To: oracle-l@xxxxxxxxxxxxx Subject: CBO irregularity The CBO has been nothing short of a pain in the butt to me. Going from Development to QA to a live environment achieves unexpected results. It seems that you never know what you are going to get when it comes to an execution plan. The developers run Oracle on their Windows box and the execution path is one way, but when it gets moved to a QA environment it chooses another way. At least with the RULE base optimizer you know what you are going to get. Sometimes I think I am the only one with this problem. How do you work this? Do you always use hints, do you use stored outlines....? Thanks, Rick Stephenson ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------