|
Hi JustinMy understanding is that the system is building an index over the file for use by a query (in the SQL sense of the word) of some sort. Since the index the SQL optimizer has determined is required to run the query does not exist (or has not been located) the system is building it.
Hope this helps Regards Evan Harris At 09:16 a.m. 7/12/2005, you wrote:
Hopefully someone can answer this for me in easy terms. Why would a system rebuild access paths for files when being used by many ODBC (QZDASOINIT) jobs? For example, the jobs will sometimes go in to an IDX-xxxxxxx where xxxxxxx = the name of a file. The online help shows that the IDX status means it's rebuilding the index (access path) to whichever file it's listing. What prompts the rebuild? Is there somewhere we could go look to see why it's doing that? Additionally, in Performance Navigator there's a chart for Index Rebuilds/second - the online help for describing why is pretty vague there also. Please advise - thanks in advance for your help and for not biting my head off if this is basic and I just never learned it - hah! -- Justin C. Haase - iSeries System Engineer IBM Certified Systems Expert - eServer i5 Kingland Systems Corporation
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
