Re: Longtx transaction log help

You could also redirect the logs and backup device to /dev/null and let IDS to automatically backup them. A level 0 archive this way takes nothing to change the login mode of your database. J. mosserp@wellsfargo.com wrote: >>-----Original Message----- >>From: owner-informix-list@iiug.org >>[mailto:owner-informix-list@iiug.org] On Behalf Of Gary Quiring >>Sent: Friday, April 22, 2005 12:27 PM >>To: informix-list@iiug.org >>Subject: Longtx transaction log help >> >>I am trying to move some data to a 9.4UC5 server and am stuck >>on the indexing >>piece. I used myschema and dbcopy from Art to migrate the >>data. The dbcopy >>went fine but when I apply the 2nd schema which has the >>indexes I keep getting a >>long transaction error. >> >>I have 195 transaction logs configured when I run onstat -l > > > <snipped> > > Gary, > > Switch the database to non-logging, do the build of the indexes & > constraints, then switch it back to the appropriate logging mode > (buffered or unbuffered or ansi). > > HTH, > Paul Mosser > > sending to informix-list > sending to informix-list

"Jean Sagi" <jeansagi@myrealbox.com> wrote in message news:1114277905.df63baa2cee2a38df035e605293a4c3f@teranews... > > You could also redirect the logs and backup device to /dev/null and let > IDS to automatically backup them. > Yeah, you could, but discarding the logs in this way will not help him one iota with a long transaction issue. Paul Mosser's remedy - temporarily change the logging mode of the database - is spot on. Neil Truby Ardenta Limited