age-
From: Allen Egerton
To: U2 Users List
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 to the
hysical disk location of the
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
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
om: Wally Terhune
To: U2 Users List
Sent: 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
, 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
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?
o:u2-users-boun...@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
hune
> > 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-
>
-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.
237 ..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]
---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 Unida
-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
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(
13 matches
Mail list logo
