Databases
StackOverflow2013
Postsdbo
POQuery not using Index --
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQuery not using Index --
    primarykey
    data
    text
    <p>My question concerns Oracle 11gr2 and the use of indexes in SQL queries. Please help me with issue below, I am unable to use index on this query:</p> <pre><code>SELECT ListingManagerID, FirstName, LastName, PrimaryPhone, AlternatePhone, Email, UserName, Password, RecallGuid, CustomerSince, PWChangeRequired, PWExpireDate, CallingHours, CreateDate, CreateIPAddress, LastLogin, AutoRenewFlag, LastUpdated, UpdatedBy, AutoRenewRemovedDate, AutoRenewDate, isSupplier, PrefferedLanguage, AboutMe, PictureFilePath, IsProfilePictureDisplay, LocaleID, Address1, Address2, CityID, CountryID, StateProvinceID, PostalCode, RegistrationSource, PPCTypeID, GhostUser, ProfileId, TimezoneID, OCA FROM ListingManager WHERE trim(lower(LISTINGMANAGERID)) = 'e.kkagacoe4aaae7rnr9lua5' </code></pre> <ol> <li>Created Index</li> </ol> <p><code>SQL&gt; CREATE INDEX IDX_LISTINGMANAGER_ID ON listingmanager (LOWER(listingmanagerid));</code></p> <p>Index created.</p> <ol> <li>Gather Statistics</li> </ol> <p><code>SQL&gt; EXEC DBMS_STATS.GATHER_TABLE_STATS('INTERSHOP', 'LISTINGMANAGER' , CASCADE=&gt;TRUE);</code></p> <p>PL/SQL procedure successfully completed.</p> <p>Index was created on <code>Listingmanager Column</code>, But still Execution plan is showing full table scan. I don't know why full table scan happening still.</p> <p>ListingManagerID is the primary key of the table, can I modify index created by primary key?</p> <pre><code>PLAN_TABLE_OUTPUT -------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| -------------------------------------------------- | 0 | SELECT STATEMENT | | 2013 | 487K| 1784 (1)| |* 1 | TABLE ACCESS FULL| LISTINGMANAGER | 2013 | 487K| 1784 (1)| </code></pre> <p>Predicate Information (identified by operation id):</p> <pre><code>1 - filter(TRIM(LOWER("LISTINGMANAGERID"))='e.kkagacoe4aaae7rnr9lua5' ) </code></pre> <p>Thanks</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJustin
    1. USAryan johan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POQuery not using Index --
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POQuery not using Index --
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. POQuery not using Index --
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would guess this is Oracle, given the reference to PL/SQL - but I shouldn't *have* to guess. Please add an appropriate tag for your RDBMS (especially since indexing and tuning is highly DB specific)
      singulars
      1. POQuery not using Index --
      1. USDamien_The_Unbeliever
    2. CODoes it work if you remove the 'trim' from the table-side of the WHERE clause? Can't you normalise your table data to be trimmed? Does it help if you add a computed trimmed + lowered column then index and query that?
      singulars
      1. POQuery not using Index --
      1. USRup
    3. CO@Rup - Yes, Its uses the Index if remove "trim"
      singulars
      1. POQuery not using Index --
      1. USAryan johan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload