Re: adding rowids to a frag'd table

Long transaction rollback is only caused by filling the logical logs past the LTXHWM Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Tue, Nov 3, 2009 at 8:23 AM, <Darren_Jacobs@carmax.com> wrote: > > IDS 10 FC8 > HPUX 11 > > Greetings > > I'm in the process of altering a 22 mil row table frag'd across 4 dbspaces > to accomodate connectivity through windoze SSIS which is dependant upon the > rowid. Why...I don't know....is sqeal! > > Anyway, I keep running into a long trans. I've dropped all the indexes, > altered the table to raw, locked the table in exclusive to avoid blowing > the locks, and I still run into a long trans. This is a test system I'm > running this on so there is little or no other activity running. There are > approx 120 logs at 100 meg each. I know I'm not filling 50% of the logs. > I'm also not blowing space. > > Other than unloading, dropping, recreating the table with rowids, does > anyone have other ideas? or what may be causing the long trans? > > Thanks! > > ======================== > Darren Jacobs > Sr Database Analyst > Darren_Jacobs@carmax.com > 804.747.0422 x3221 > ======================== > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >