Yep. I've been burned on concurrent myself. So I guess I should rephrase... Only use RESIZE if the file is idle.
On 7/2/12, Wjhonson <wjhon...@aol.com> wrote: > > Personally I don't trust CONCURRENT > It's like tiny bits flying back and forth over my head in a helter-skelter > mishmash > But maybe I'm too old school > > Perhaps if they came out and explained exactly how it's doing this, I'd feel > more confident in using that. > > > > > > > > > -----Original Message----- > From: John Thompson <jthompson...@gmail.com> > To: U2 Users List <u2-users@listserver.u2ug.org> > Sent: Mon, Jul 2, 2012 11:28 am > Subject: Re: [U2] File error > > > If this is universe- the RESIZE command might have an option to > onvert it. My disclaimer is that I have never tried such a thing and > ou should make a backup first :) > On 7/2/12, Wjhonson <wjhon...@aol.com> wrote: > > Personally, what I would do right now, is to create another file as your > "temporary holding place" if you will. > Then select, perhaps on a date range, everything earlier than... 2005 or > whatever, and read it, write it to the new location and delete it from > where > it's at. > That will solve your problem *today* which it that NO NEW RECORDS can be > written. Big problem isn't it? > > Now how to solve your problem tomorrow? > You can make it 64BIT which might be a nice weekend overtime job for you > Or you can decide to create a distributed file, which again means you need > an exclusive file lock. > > So hopefully they can live with not being able to access these old records > for a week. > > > > -----Original Message----- > From: mhilbert <mhilb...@ppcsoftware.com> > To: u2-users <u2-users@listserver.u2ug.org> > Sent: Mon, Jul 2, 2012 9:02 am > Subject: Re: [U2] File error > > > If this were a dynamic file, you would have to create a new file adding > the phrase 64BIT. > I don't know if the phrase is valid for non-dynamic files. > On Mon, 2 Jul 2012 10:20:13 -0500, Holt, Jake wrote: > We are getting the message: > > Warning: Attempt to extend file "GJ/INV" beyond the 2 gigabyte file > limit. 32-bit static hashed or dynamic files cannot exceed a file > size > of 2 GB. Use a distributed or 64-bit file. > > I get why we're getting the message, I'm wondering, what is the > easiest/safest way to fix it? I could purge records if necessary > but > they would prefer not doing this. > > We're running 10.0.21 on Windows server 2003 32 bit. > > Thanks, > > Jake > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ > 2-Users mailing list > 2-us...@listserver.u2ug.org > ttp://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > > -- > ent from my mobile device > John Thompson > ______________________________________________ > 2-Users mailing list > 2-us...@listserver.u2ug.org > ttp://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- Sent from my mobile device John Thompson _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
