Re: HELP - Logical Logs are full - Online halted

I'd found a tricky solution,which you can use without losing any data or being obliged to go back to arcive time state. If your problem has continued yet,inform me. --Babak > From jleffler@earthlink.net Thu Apr 29 07:10:18 1999 > From: Jonathan Leffler <jleffler@earthlink.net> > To: informix-list@iiug.org > Subject: Re: HELP - Logical Logs are full - Online halted > Date: Wed, 28 Apr 1999 03:56:49 -0700 > X-List-Gateway: comp.databases.informix > > zigzag@infi.net wrote: > > > > Can anyone assist with the following problem: > > 1) Very long transaction aborted (loading of large table) > > 2) Appears that logical logs are completely full and transaction > > can not roll back. > > 3) Informix Online was taken offline and restarted > > 4) Online will not "recover" from recovery mode. > > 5) tbstat -m (log file display) says logical logs are full and need to > > backed up. > > 6) can't get online to quiescent mode or to online mode. > > > > This Online 4.1 Engine running on ISC Unix. > > > > Please help. Production system has halted. > > If you don't have a support contract, yesterday would have been a > good time to take one out. Informix Tech Support may be able to help > you, but to fix this requires some jiggery pokery with the raw data > on disk, basically fibbing to the system, which is apt to lead to > other problems if not done very carefully, which is why Informix does > not let untrained people (eg me) do such things. > > On the other hand, v4.1 on ISC Unix is probably 386/ix, and is very > old indeed. There's a high chance you've let your support lapse, > probably because you are unable to get upgrades for your platform. > That will make Informix Tech Support somewhat less sympathetic to > your plight -- but try them anyway. Also, it may take time to locate > the software necessary for a 4.1 system; they're not the mainstream > versions any more, and haven't been for (conservatively) five years > and more. > > If that doesn't work, then you're reduced to a full recovery from > your archives -- you do have good backups, don't you? > > How did you land yourself in this problem? Why didn't you look at > the size of your LOAD operations and either use DBLOAD (which can > break a single load into sub-transactions of a configurable size) or > multiple data files? You'll need to know about this to avoid the > problem a second time. > > -- > Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) > Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN > #include <disclaimer.h> > >