Re: no logging database - long transaction aborted

I doubt setting the tape device to /dev/null helps. Creating index is one single transaction. You get a long transaction error whenever this transaction is bigger than a pre-determined percentage (LTXHW) of total logical logs size. The logical logs will not be backed-up until this transaction is over - by which time you have already hit LTXHW. Two solutions: 1. Add more logical logs. or 2. Unload table, drop and re-create the table with the "index built". Then load the rows back into the table. UPDATE STATISTICS. On Fri, 31 Jul 1998 03:22:14 GMT, Nils.Myklebust@nmdata.com (Nils Myklebust) wrote: > >It may also be enough to set the log backup tape device in the >onconfig file to /dev/null if that isn't allready done. Then logs will >be "backed up" into oblivion automatically and freed. If the database >isn't loged anyway you hardly need the logs of such statements. > > >Nils Myklebust >NM Data AS >Norway >E-mail: Nils.Myklebust@nmdata.com >FAQ at: http://www.iiug.org/techinfo/faq/faq_top.html >(Now with ODBC info under "Third party products".)