> We are attempting to add nearly 1.8 millions records to a TI
dataset.
> Suprtool is the means. After 95% of the file is processed:
>
>  **** STALLED TRANSACTION: EXCEEDED ACCUMULATED LOG DATA THRESHOLD

Typically, any time you're doing huge additions or changes, you want
to
  Turn off logging
  Turn off native sorted-sequential or third-party index features,
except for hugely-expensive full-text index setups

Writing out gigabytes of changes to a log is usually a waste of time;
if it blows up, you know what you did, you have a copy of what you
started with, so you do it again. Similarly, except in the case of
full-text index files that are hellaciously expensive to build, native
sorted-sequential or third-party index setups quickly reach the
breakpoint where it is faster and easier to completely re-create the
index after all the changes are done than it is to maintain the index
through millions of add/update operations.

Based on the known-starting-point/known-changes scenario, I guess you
might make a case for completely detaching the database from XM,
though I don't know that such a thing can be done. But you definitely
don't--with the cited exception--want to be updating the index files
through XM.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *