--- jaromir nemec <jaromir@xxxxxxxxxxxx> wrote: > > > Simple the DBMS will suppress any ORA-nnnnn error and will try in a loop the > next access path. May be next time the query will be successful! > > How many time this loop on different execution plans should be repeated? Why > not limit it with OPTIMIZER_MAX_PERMUTATIONS:) > I disagree, this approach will bring out more issues with query performance. Plus how will the rdbms *know* what results you want to keep trying to please you? Maybe I *want* the rdbms to error out on the first invalid datum as it does now. So, if there are any issues I'd like to know now rather than tomorrow when it comes back with 15 rows and 25000 invalid rows after traversing 80000 different paths of execution. JWOR ... Just waste of Resources. Cheers Raj ===== Best Regards Raj --------------------------------------------------------- select mandatory_disclaimer from company_requirements; __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---------------------------------------------------------------- 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 -----------------------------------------------------------------