Thanks Wally. In this situation we suspect that the index was rebuilt while some users had the file open (via SB+ cached file buffers) and those users were the ones entering transactions that didn't get updated into the index. We logged everyone off last night and rebuilt the index and so far today things appear to be better.
On Fri, Sep 9, 2011 at 6:30 AM, Wally Terhune <wterh...@rocketsoftware.com>wrote: > Kevin: > The things you need to review: > 1) LIST.INDEX WO ALL DETAIL - to examine the index definitions and details > of keys in the file > 2) From the shell, without the file being updated: guide_ndx -x3,all WO > Review the output file GUIDE_XERROR.LIS for physical or logical > corruption > 3) UDT.OPTIONS active (per Mecki's comment about leading 0s) > > Wally Terhune > U2 Support Architect > Rocket Software > 4600 South Ulster Street, Suite 1100 ..Denver, CO 80237 ..USA > Tel: +1.720.475.8055 > Email: wterh...@rs.com > Web: www.rocketsoftware.com/u2 > > > > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org [mailto: > u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King > Sent: Thursday, September 08, 2011 9:09 PM > To: U2 Users List > Subject: Re: [U2] Unidata 7.1.22 Index Issue > > What can I get you Wally? We did a CREATE.INDEX WO SHOP.CODE NO.NULLS > followed by BUILD.INDEX WO SHOP.CODE. The index seems to work fine > immediately after. If the shop code in the record changes, however, the > index does not seem to reflect the change. This is evidenced by: > > DISABLE INDEX WO > SELECT WO WITH SHOP.CODE = "09" > 21 items selected > CLEARSELECT > ENABLE.INDEX WO > SELECT WO WITH SHOP.CODE = "09" > 19 items selected > CLEARSELECT > DISABLE.INDEX WO > SELECT WO WITH SHOP.CODE = "09" > 21 items selected > > What else can I get you? > > On Thu, Sep 8, 2011 at 5:58 PM, Wally Terhune > <wterh...@rocketsoftware.com>wrote: > > > Not enough information. > > > > Wally Terhune > > U2 Support Architect > > Rocket Software > > 4600 South Ulster Street, Suite 1100 ..Denver, CO 80237 ..USA > > Tel: +1.720.475.8055 > > Email: wterh...@rs.com > > Web: www.rocketsoftware.com/u2 > > > > > > > > -----Original Message----- > > From: u2-users-boun...@listserver.u2ug.org [mailto: > > u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King > > Sent: Thursday, September 08, 2011 5:42 PM > > To: U2 Users List > > Subject: [U2] Unidata 7.1.22 Index Issue > > > > We have a customer on Unidata 7.1.22 running the Prelude application. > They > > have an index on a field in a file that looks like this: > > > > Top of "SHOP.CODE" in "DICT WO", 9 lines, 82 characters. > > *--: P > > 001: V > > 002: EXTRACT(@RECORD,110,2,0) > > 003: > > 004: Shop Code > > 005: 2L > > 006: S > > 007: > > 008: SHOP.CODEýýEXTRACT(@RECORD,110,2,0) > > 009: WO > > Bottom. > > > > Because this field is extracting from @RECORD, we should be able to index > > it > > without problems, right? However, the reality is starkly different. The > > other data indexes work fine, but this derived index does not seem to be > > getting updated properly. > > > > -Kevin > > http://www.PrecisOnline.com > > _______________________________________________ > > U2-Users mailing list > > U2-Users@listserver.u2ug.org > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > > U2-Users mailing list > > U2-Users@listserver.u2ug.org > > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > > > > -- > -Kevin > http://www.PrecisOnline.com > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- -Kevin http://www.PrecisOnline.com _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
