On Sep 29, 2008, at 5:52 AM, A.C.P.Crawshaw wrote:
> We have a journalled Ingres 2.0 database (we're on extended
> support) which writes
> journal files infrequently.
> ... The daytime activity appears insufficient to force journal
> file writes, so I'm worried that a disk crash late in the afternoon
> would cause us to
> lose the day's transactions.
>
First, check the archiver_interval configuration parameter to
make sure it's 1. Also double check your consistency point
interval (cp_interval) to make sure that it's not too big.
A rough guideline for CP interval would be a percentage that
works out to 50 Mb of transaction log, and plus or minus
25 Mb or so is fine. (Avoid CP intervals that are more
than about 20% of the transaction log, you can get into
logfull issues that way unless you do extremely little
updating.)
If the configuration is OK, you might simply not be updating
much during the day. You can issue periodic DM1314 trace
points to force an archiver cycle every hour or so if you
like. You might want to precede the DM1314 with a DM1305
to also force a consistency point (or, use the cp_timer
config parameter of the recovery server); if the installation
really is that light on updating, the extra CP's won't hurt,
and will afford a little extra safety against massive disk
failure.
Karl
>> Stay informed about: Journal size/frequency