Re: [U2] Unidata 7.1.22 Index Issue

2011-10-13 Thread regalitare
: Fri, Sep 9, 2011 7:36 pm Subject: Re: [U2] Unidata 7.1.22 Index Issue NO. was mostly trying to point out that you need to be specific about what perations you have done regarding index refreshing. 'rebuild' is unspecific. For logical integrity issues - which generally occur because folks

Re: [U2] Unidata 7.1.22 Index Issue

2011-10-13 Thread Allen Egerton
Were these files by any chance copied/moved from their original location? The headers to the file, (at least in Universe), create pointers to the physical disk location of the indexes, and if you move the file without adjusting those pointers, you can have all sorts of fun issues. On 10/13/2011

Re: [U2] Unidata 7.1.22 Index Issue

2011-10-13 Thread Colin Alfke
We came across this a few years back when moving and copying files at the OS level (usually copying the data file but not the associated index). What's even easier than creating a dummy index (especially on a large file) is to simply copy another files index (X_smallfilename) to your working file

Re: [U2] Unidata 7.1.22 Index Issue

2011-10-13 Thread regalitare
Egerton aeger...@pobox.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, Oct 13, 2011 10:21 am Subject: Re: [U2] Unidata 7.1.22 Index Issue Were these files by any chance copied/moved from their original location? The headers to the file, (at least in Universe), create pointers

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-09 Thread Mecki Foerthmann
You may have a problem with leading zeroes. Are there by any chance 2 records with 9 in Record120,2? On 09/09/2011 04:08, Kevin King wrote: 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

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-09 Thread Wally Terhune
...@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

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-09 Thread Kevin King
: +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

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-09 Thread Wally Terhune
...@listserver.u2ug.org] On Behalf Of Kevin King Sent: Friday, September 09, 2011 11:57 AM To: U2 Users List Subject: Re: [U2] Unidata 7.1.22 Index Issue 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

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-09 Thread Kevin King
Am I understanding you correctly Wally that if an index becomes corrupted for any reason the index is to be deleted, then recreated, and THEN rebuilt? And in a related question, am I understanding you to say that an index cannot (should not) be rebuilt without being deleted and recreated?

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-09 Thread Wally Terhune
, September 09, 2011 5:20 PM To: U2 Users List Subject: Re: [U2] Unidata 7.1.22 Index Issue Am I understanding you correctly Wally that if an index becomes corrupted for any reason the index is to be deleted, then recreated, and THEN rebuilt? And in a related question, am I understanding you to say

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-08 Thread Wally Terhune
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

Re: [U2] Unidata 7.1.22 Index Issue

2011-09-08 Thread Kevin King
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