Hello,

in this mailinglist, I have often read about things that can
be done when something goes wrong (for example, gfix -sweep,
or backup and restore the database). I wonder whether there
are things to be done if _nothing_ goes wrong?

According to The Book, the only danger seems to arise when
the 32-bit transaction counter wraps to 0 (or -2^31?).
(Or is it a 64-bit counter meanwhile? SS 2.0.3.12981.0-r6
running here. No 2.0.4 available, 2.1 not "stable" yet,
Gentoo says.)

I'm just a bit concerned if there's really "nothing to do"
for me as database administrator - but if it's really like
that, so much the better!

-Matt

PS: Example (the "most heavily used" database):

Database "/var/fbdata/wddx.fdb"
Database header page information:
Flags 0
Checksum 12345
Generation 1555634
Page size 4096
ODS version 11.0
Oldest transaction 1555626
Oldest active 1555627
Oldest snapshot 1555627
Next transaction 1555628
Bumped transaction 1
Sequence number 0
Next attachment ID 0
Implementation ID 19
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 3
Creation date Sep 23, 2007 10:03:05
Attributes force write

Variable header data:
Sweep interval: 20000
*END*


Database file sequence:
File /var/fbdata/wddx.fdb is the only file

Analyzing database pages ...
HTTP (128)
Primary pointer page: 157, Index root page: 158
Data pages: 156823, data page slots: 156823, average fill: 83%
Fill distribution:
0 - 19% = 0
20 - 39% = 1
40 - 59% = 0
60 - 79% = 385
80 - 99% = 156437

Index IDATETIME (0)
Depth: 3, leaf buckets: 9071, nodes: 4428059
Average data length: 2.34, total dup: 511865, max dup: 14
Fill distribution:
0 - 19% = 0
20 - 39% = 1
40 - 59% = 1
60 - 79% = 0
80 - 99% = 9069

Index PK_HTTP (1)
Depth: 3, leaf buckets: 6614, nodes: 4428059
Average data length: 1.01, total dup: 0, max dup: 0
Fill distribution:
0 - 19% = 0
20 - 39% = 0
40 - 59% = 0
60 - 79% = 1
80 - 99% = 6613