Re: Long transaction error with no-log

"Leonid Belov" <white@intek.spb.su> wrote: :Hi all, :I have a database with no logging under Informix-Online 7.11. :This database contains a big table. :When I try to update every row in this table using single UPDATE statement, :it stops with error :-458 Long transaction aborted :caused by logical log's overfull. :Why server writes UPDATE activity log for no-logging database? If logging is realy turned off there should be no log activity for an update statement. (Create table and inserts that leads to new extents beeing alocated are still logged.) :I don't want to increase number of logical logs because of disk space limit. :More, I don't need any logging for this operation. :Is there any method to work it around without dbunload/dbload - :for example, switch off activity logging for this table/database? :Any help would be appreciated Have logging been turned on before? If so, are you sure you have realy turned off logging (including a full level 0 backup)? RTFM on exactly how to do it. If you want this backup to be fast, and you don't need the backup, you may temporarily set backup to /dev/null. Just remember to set it back to your tapedrive afterward so you do get real backups later. Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org