suche 36x36
  • Admin-Scout-small-Banner
           

    CURSOR Admin-Scout

    get the ultimate tool for Informix

    pfeil  
Latest versionsfixlist
14.10.xC10 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT29124 Status: Closed

ONCHECK -PT INDEX USAGE INFO IS NOT UPDATE CORRECTLY

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
When doing a simple select with an index scan, oncheck -pt will
still show the index not being used.
This is true both for a key only scan and an index read.

For a repro, just do an select zipcode  from customer or use an
optimizer hint to force an index scan on

set explain on;
select {+INDEX(customer zip_ix)}
fname, lname, zipcode from customer


sqexplai will show the index being used, but cases oncheck -pt
will not show any index access use..

Index zip_ix fragment partition rootdbs in DBspace rootdbs

    Physical Address               1:58240
    Creation date                  04/12/2019 12:20:34
    TBLspace Flags                 801        Page Locking
                                              TBLspace use 4 bit
bit-maps
    Maximum row size               134
    ...
    Number of rows                 0
    Partition partnum              1049234
    Partition lockid               1049211
    Last Lookup/Scan               No Record





the accesstime is updates via the IDX_ACCESS_NOW marcro, which
is only called in rsreadidx and btset_pos_at_item.
These functions are seemingly not used in the above scenario.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of IDS prior to 12.10.xC13.                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* oncheck -pt index usage info is not updated correctly.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.05.2019
24.09.2019
24.09.2019
Problem solved at the following versions (IBM BugInfos)
12.10.xC13
Problem solved according to the fixlist(s) of the following version(s)
Informix EditionsInformix Editions
Informix Editions
DocumentationDocumentation
Documentation
IBM NewsletterIBM Newsletter
IBM Newsletter
Current BugsCurrent Bugs
Current Bugs
Bug ResearchBug Research
Bug Research
Bug FixlistsBug Fixlists
Bug Fixlists
Release NotesRelease Notes
Release Notes
Machine NotesMachine Notes
Machine Notes
Release NewsRelease News
Release News
Product LifecycleProduct Lifecycle
Lifecycle
Media DownloadMedia Download
Media Download