|Subject||Re: [firebird-support] Should autosweep be happening on that database?|
I`m not sure if running a 24/7 trace is a good idea (database is under relatively heavy load). Anything else I could do to help?
btw I am noticing that the unexpected sweep is about 27000-30000 transactions after the scheduled one. I could send a log if that helps in any way. I set the interval to 100000 and in a day or two I`ll know if it still runs by its own.
2014-10-27 21:46 GMT+02:00 Thomas Steinmaurer ts@... [firebird-support] <email@example.com>:
Yes, by setting the sweep interval to 0, automatic sweeping should be> I did some reconfiguration on a database yesterday, so I`m monitoring
> the logs for any issues and I noticed something strange :
> Mon Oct 27 16:54:25 2014
> Sweep is started by SYSDBA
> Database "orbis-aton"
> OIT 21080, OAT 21081, OST 20456, Next 44177
> (yes, I know it`s a bad idea but all database connections are by SYSDBA)
> I don`t remember running a sweep (logs say I wasn`t even logged in at
> the time) and nobody else has access (or knowledge, for that matter) to
> run a sweep on that machine so I got curious.
> Logs say an unexpected sweep has been running basically every day
> (sometime between 5 and 10 pm, which is apparently when it hits the
> number of transactions). I have a manual sweep at 5:40am in cron and I
> checked - configuration is correct and runs as expected. I also
> double-checked gstat :
> Database header page information:
> Flags 0
> Checksum 12345
> Generation 51454
> Page size 16384
> ODS version 11.2
> Oldest transaction 21357
> Oldest active 50561
> Oldest snapshot 49520
> Next transaction 51318
> Bumped transaction 1
> Sequence number 0
> Next attachment ID 130
> Implementation ID 24
> Shadow count 0
> Page buffers 0
> Next header page 0
> Database dialect 3
> Creation date Oct 26, 2014 12:28:26
> Attributes force write
> Variable header data:
> Sweep interval: 0
> Shouldn`t automatic sweep be disabled or have I misread the
> documentation? FB version is 2.5.3.
disabled. There is also: http://tracker.firebirdsql.org/browse/CORE-4100
(marked as fixed in 2.5.3) but you are mentioning that you are using
2.5.3, although I'm not entirely sure if CORE-4100 applies to sweep
interval = 0 anyway.
You could use the Trace API to trace services API requests to get a
clearer picture on what client application is causing the sweep in case
it has been triggered manually.
Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.