Re: Table Access By Index Rowid
- From: "Daniel W. Fink" <Daniel.Fink@xxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Fri, 13 Aug 2004 13:31:34 -0600
In your predicate, you have several conditions that the rows retrieved
from PROFILEDUSER table must meet. Until the row is retrieved from the
table, the ability of the row to meet the predicate conditions are not
known. In this case, it looks to me that 1664 rows matched the predicate
condition for the unique index (on profileduserid?), but only half of
those rows matched the other conditions (hsbc_user_category,
business_country_id, processed and region)
Regards,
Daniel
jaysingh1@xxxxxxxxxxxxx wrote:
> FROM (SELECT * FROM PROFILEDUSER WHERE hsbc_user_category IN
>('GCAT','HCAT')) P,
> WHERE P.profileduserid= e.profileduserid
> AND P.business_country_id = c.countryabbrev
> AND p.processed_by in ('3')
>and p.region in ('4051')
>and p.business_country_id='GB'
>
>Rows Row Source Operation
>------- ---------------------------------------------------
> 0 COUNT STOPKEY
> 0 VIEW
> 0 MERGE JOIN CARTESIAN
> 1 NESTED LOOPS
> 833 TABLE ACCESS BY INDEX ROWID EXTENDEDATTRIBUTES
> 2838 INDEX RANGE SCAN DESCENDING (object id 1174163)
> 832 TABLE ACCESS BY INDEX ROWID PROFILEDUSER
> 1664 INDEX UNIQUE SCAN (object id 5840)
> 0 SORT JOIN
> 0 TABLE ACCESS BY INDEX ROWID COUNTRIES
> 0 INDEX RANGE SCAN (object id 1131957)
>
>
>
----------------------------------------------------------------
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
-----------------------------------------------------------------
Other related posts:
