Re: Track all records read from a table -- MIDRANGE-L

Subject: Re: Track all records read from a table
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Tue, 22 Mar 2016 13:53:31 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Tue, Mar 22, 2016 at 12:57 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I agree. However, it won't help the OP with the performance hit caused

by

read triggers.

Seems rather odd to me that database I/O is cached by default. But you have
to license that feature for journals.

Journal entries _ARE_ cached by the base OS, but only if you're using
commitment control. When using commitment control, commiting the changes
also writes the cached journal entries to disk.

Otherwise, for resiliency, the journal

entry is written to disk right away.

The HA Journal Performance LICPGM option was originally Batch Journal
Caching PRPQ (5799-BJC).

More info here in the Striving for Optimal Journal Performance REDBOOK
https://www.redbooks.ibm.com/abstracts/sg246286.html

Charles

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.