RE: How to avoid an index that is part of a view

From: Mercadante, Thomas F \(LABOR\) <Thomas.Mercadante_at_labor.state.ny.us>
Date: Fri, 18 Aug 2006 14:25:28 -0400
Message-ID: <ABB9D76E187C5146AB5683F5A07336FF68151B@EXCNYSM0A1AJ.nysemail.nyenet>

You can always use the standard:

and column + 0 = number_value

and column || '' = 'string value'

This transmission may contain confidential, proprietary, or privileged information which is intended solely for use by the individual or entity to whom it is addressed. If you are not the intended recipient, you are hereby notified that any disclosure, dissemination, copying or distribution of this transmission or its attachments is strictly prohibited. In addition, unauthorized access to this transmission may violate federal or State law, including the Electronic Communications Privacy Act of 1985. If you have received this transmission in error, please notify the sender immediately by return e-mail and delete the transmission and its attachments.

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Hameed, Amir Sent: Friday, August 18, 2006 2:22 PM
To: oracle-l; Wolfgang Breitling
Subject: How to avoid an index that is part of a view

I have a query that is referencing a column in its where clause which is part of a view. The column in the view has an index which is not very selective. This index's table is a standard Oracle Apps table and therefore we can not tinker with its indices. I would like to avoid the optimizer from using the index which part of the view. How do I do it:

Thanks
^Amir

--

http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Fri Aug 18 2006 - 13:25:28 CDT