Re: Two users, one query, two optimizer plans

Mu guess is that dm_issuegrant_ix01 is a function based index designed to apply to: hextoraw(value).
When user A run there is no where clause that fits the index, so full table scan.

Have you tried doing the select with the same where clause (including hextoraw) from user A?

Adar Yechiel
Rechovot, Israel



Paul Baumgartel wrote:


For each table subject to row-level security policy, the RLS view is of the form

SELECT <columns> FROM <table> WHERE company_fk in (hextoraw('<value>')

My theory at this point is that RLS is causing the discrepancy in optimizer plans. Has anyone seen this? Is there another reason why the plans would differ?

Thanks,


--
Paul Baumgartel
paul.baumgartel@xxxxxxxxxxxx <mailto:paul.baumgartel@xxxxxxxxxxxx>

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


Other related posts: