Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Walt Hultgren {rmy} — — source: Informix-list mailing list archive (1991-1998)
Path: emory!swrinde!cs.utexas.edu!usc!orion.oac.uci.edu!ucivax!george
From: george@brooks.ics.uci.edu (George Herson)
Newsgroups: comp.databases.informix
Message-ID: <2936F200.22922@ics.uci.edu>
Date: 30 Nov 91 02:05:52 GMT
Reply-To: george@ics.uci.edu (George Herson)
Organization: UC Irvine Department of ICS
Nntp-Posting-Host: brooks.ics.uci.edu
We're having problems with our unix (sequent Dynix/ptx) based
Informix On-Line. A coworker reports that always, after 2000
transactions, the log file becomes full and no more updates or
inserts are allowed. Performing a total archival backup is
the only method that seems to clear the transaction log. Are
there any other ways to clear the log???
In what he thinks is a related problem, I get a -134 error,
which is an ISAM "no more locks" error indicating that the
shared memory parameter for the maximum number of locks was
exceeded. The problem with that diagnosis by Informix is that
it happens whenever I have two processes examining different
records on the same tiny, row-level locked table. No way has
2000 locks been exceeded; I'm developing right now with tiny
test tables.
Anyone have any ideas?
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.