Re: Informix Transaction Logging

tell us about the log parameters and how many log pages are getting chewed up. Nona >Subject: Informix Transaction Logging >From: "Mike Bloom" mbloom@erols.com >Date: 08.07.00 17:18 W. Europe Daylight Time >Message-id: <8k7gov$7ek$1@bob.news.rcn.net> > > I have a question about transaction logging in Informix Dynamic Server >7.3 Our database is in unbuffered logging mode. When I issue an SQL >command in dbaccess, such as "DELETE FROM table1", I soon get an SQL 458 >error message - "Long Transaction aborted". There are about 50,000 rows >in this table. I am not issuing a BEGIN WORK statement, so I am curious as >to why transaction logging is still occuring. > To make matters more confusing, we have another database instance (also >in unbuffered logging mode) on our machine and when I issue a "DELETE FROM >table1" command in dbaccess in the other instance, it works fine. The table >in this other instance still has 50,000 rows in it. However, the >transaction log files do not appear to be growing in size when issuing this >command in the second instance. This is the behavior I would expect if I do >not issue a BEGIN WORK statement. > Can somebody shed some light on this as to why I may be getting this >long transaction error message when I have not specified a BEGIN WORK >statement? Thanks. > > - Mike Bloom > mbloom@erols.com > > > > > > > >