|
midrange.com
We ran in to the same thing where I work. We were seeing thru Performance
navigator 2 -3 index rebuilds per second. I then ran STRDBMON for several
minutes and ended it. I then queried the file it produced and found that
what was happening it the ODBC queries were building their own indexes and
when done throwing them away. So I worked with one of our programmers and
he created about 50 of the indexes that the ODBC queries were building and
we now build about .8 per second. Our ODBC users are much happier.
John Bresina Jr
Sr Server Engineer - Midrange Team
Allianz Life of North America
5701 Golden Hills Drive
Minneapolis, Mn 55416
763 582 6761
"Haase, Justin
C."
<justin.haase@Kin To
gland.com> "Midrange Systems Technical
Sent by: Discussion"
midrange-l-bounce <midrange-l@xxxxxxxxxxxx>
s@xxxxxxxxxxxx cc
Subject
12/06/2005 02:16 Access path / index rebuilds
PM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
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
CONFIDENTIALITY NOTICE: This e-mail communication, including attachments,
is covered by the Electronic Communications Privacy Act, 18 U.S.C.
2510-2521, is confidential, and may be legally privileged. If you are not
the intended recipient or believe you received this communication in error,
please reply to the sender indicating that fact and delete the copy you
received. In addition, retention, dissemination, distribution, copying, or
otherwise use of the information contained in this communication is
strictly prohibited. Thank you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
-----------------------------------------
CONFIDENTIALITY NOTICE: The information in this message, and any files
transmitted with it, is confidential, may be legally privileged, and
intended only for the use of the individual(s) named above. Be aware
that the use of any confidential or personal information may be
restricted by state and federal privacy laws. If you are not the
intended recipient, do not further disseminate this message. If this
message was received in error, please notify the sender and delete it.
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.
