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.
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
Jean-Brice Albertus wrote:
>
> -----Message d'origine-----
> De : Jacob Salomon <jake@garpac.com>
> Groupes de discussion : comp.databases.informix
> Date : vendredi 2 octobre 1998 19:11
> Objet : Re: Log backup on /dev/null
>
> >
> >Boy, Jean-Brice! That sounds confused! HMmm.. so do you! ;-))
> >
> >You don't need to run a log backup if the log device is /dev/null. Even
> >without continuous log backup, as soon as a log is full the engine marks
> >it as backed up. You need do nothing to mimic a backed up log.
>
> That's I was'nt sure: when all my logical logs are full, what happens ? does
> the system overwrite the older or does the system crashes ???
AHAH! Now I see your confusion. You are going from 5.xx to 7.xx. In
5.xx when a log was backed up it was marked with status flag 'F' for
free in the onstat -l report. In 7.xx the status remains 'B' for
backed up until the time comes to reuse the log entry then it is
instantly changed to 'F' and then quickly to 'C' Current. This was done
so that the onlog utility could let you look at all of the previous
logs on disk not just those that had not yet been backed up. Relax,
everything is working just fine.
David, is this one in the FAQ? I think we've seen the question in one
form or another 12 times in Sept. and Oct. alone.
Art S. Kagel
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.