Has anyone ever seen a difference in query performance due to the manner
in which the parameter QUERY_REWRITE_INTEGRITY was set? I have a UAT
environment in which this parameter is set to ENFORCED as opposed to
TRUSTED as we have it in Development. We changed it in Development to
support Function Based queries and Star Query Transformations as
recommended by the Oracle documentation.



This is a data warehouse and query performance in the UAT has been
quixotic at best. Just wondering if this could be part of it? In one
scenario, queries on tables which had no index in Development ran in
milliseconds, but the same queries in UAT took hours. There are the same
number of records in each environment.


**********************************************************************
NOTICE:
This e-mail, including attachments, contains information that may be confidential, protected by the attorney/client or other privileges, or exempt from disclosure under applicable law. Further, this e-mail may contain information that is proprietary and/or constitutes a trade secret. This e-mail, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this communication, please be advised that any disclosure, dissemination, distribution, copying, or other use of this communication or any attached document is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by reply e-mail and promptly destroy all electronic and printed copies of this communication and any attached documents. 

**********************************************************************


Oracle LazyDBA home page