Well, first of all - thank you for your time.
Trace log still showed nothing but I finally noticed a pattern and talked
to one of the devs (who didn`t know but has access to the source) -
apparently I`m going to have to strangle someone who has never seen the
size of a production database :)
Well, I`ve done two things since the last post
1 I set the sweep interval to 10 (I assume I`m far from reaching that
on a normal day)
No change - Yesterday, another unexpected sweep at 5:08:03 pm
2 I started a trace session with the suggested config (changing only DB
alias, as instructed - I
Well, I`ve done two things since the last post
1 I set the sweep interval to 10 (I assume I`m far from reaching
that on a normal day)
No change - Yesterday, another unexpected sweep at 5:08:03 pm
2 I started a trace session with the suggested config (changing only DB
alias, as
Trace config :
database orbis-aton
enabled true
print_perf true
log_sweep true
exclude_filter %RDB$%
time_threshold 0
/database
services
enabled true
log_services true
include_filter Repair Database
/services
Cron calls a simple bash script with the following command for each of the
databases :
Trace config :
database orbis-aton
enabled true
print_perf true
log_sweep true
exclude_filter %RDB$%
time_threshold 0
/database
services
enabled true
log_services true
include_filter Repair Database
/services
The database filter expects a regular expression and orbis-aton can't be
Thanks. I`ve fixed the config and started a new trace session. Now we wait
again :)
2014-10-29 21:31 GMT+02:00 Thomas Steinmaurer t...@iblogmanager.com
[firebird-support] firebird-support@yahoogroups.com:
Trace config :
database orbis-aton
enabled true
print_perf true
log_sweep
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
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-3
transactions after the scheduled one. I could send a log if that helps in
any way. I set the interval to
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?
It might be ok with a proper include filter at service level from a
Trace API POV.
The following trace configuration should be fully dedicated to sweeping
only:
