Steve wrote:
Hi folks
Is my understanding correct that auditdb will only show committed transactions?
That is its default behaviour, yes.
That is, it will not show transactions in the journal which are yet to
be committed? For example, transactions which begin in one journal and
end in a subsequent journal.
Trying to understand how I find the last committed transaction in case
of a failover.
If you have replicated iiacp.log as well as the journals iiacp.log will
show you when the archiver last ran. (It is possible the archiver has
been configured to run at timed intervals though (cp_timer), so you may
need to read the log carefully to discover when it last found something
to journal.)
Alternatively if the timestamp on the journal file is preserved you can
tell when it was last written.
You can then run auditdb with the -b flag specifying a time just before
the last archive cycle. You will probably only need to go back a
few seconds.
Roy
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)