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.
SaTriGuy — — source: Informix-list mailing list archive (1991-1998)
I have a naive and simple question: are the full contents of BLOBs
logged? I've heard contradictory assertions on this, and I want to find
out why our transaction logs are filling up so fast.
--------------------------------------------------------------------------
----------------------------------
Well, I guess that your answere about BLOBS being logged has been
answered. BLOBS in tablespaces are logged like any data. BLOBS in
blobspaces are copied to the log backup with the log file that was the
current log file when the BLOB page was updated.
However, your real question was why the transaction logs are filling up so
fast. Assuming that you are using blobspace blobs, the main reason that
most folk's log files fill up really fast is because they are doing
unbuffered logging. This is expecially noticable if the platform is using
4K pages. Often I've seen sites where the customer was doing a lot of
-begin work - update 1 row - commit work. In these cases, the log pages
might only have about 80 bytes of data on a 4K page.
You might want to run an onlog on the system and see what the amount of
log page is really being used. Also check the average pages per IO from
onstat -l.
Madison Pruet
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.