oldest transaction not moving

Nick Upson

unread,

Dec 15, 2021, 7:00:38 AM12/15/21

to firebird...@googlegroups.com

Hi

firebird 2.5 on centos, I've just found one of my databases has:

Oldest Transaction 14034

Oldest Active 99123456

Oldest snapshot 99123444

Next Transaction 99123499

I'm trying to understand the Oldest Transaction number in relation to the others (numbers may not be exactly correct but 14k vs 99M is the scale), there are no limbo transactions which is the only time I recall seeing this before.

I'd like to know what happened, how to fix it (preferably without downtime) and how to avoid in the future

--

Nick

Dimitry Sibiryakov

unread,

Dec 15, 2021, 7:03:08 AM12/15/21

to firebird...@googlegroups.com

Nick Upson wrote 15.12.2021 13:00:
> I'd like to know what happened, how to fix it (preferably without downtime) and
> how to avoid in the future

If this transaction is still alive - you can see it in MON$TRANSACTIONS.
If it is already dead - run sweep. Do not turn off autosweep for the future.

--
WBR, SD.

Nick Upson

unread,

Dec 15, 2021, 7:30:35 AM12/15/21

to firebird...@googlegroups.com

Hi Dimitry

its not alive, nothing for it anywhere, we'll see what it looks like after the sweep

--

Nick

--
You received this message because you are subscribed to the Google Groups "firebird-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebird-suppo...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/84d03e69-decc-b3d7-490d-adad2e00edc1%40ibphoenix.com.

Alexey Kovyazin

unread,

Dec 16, 2021, 3:34:48 AM12/16/21

to firebird-support

Hello,

run gfix -sweep

If it will be the same after the sweep, it means that something prevents sweep, probably, corrupted index - in this case, do backup/restore.

Regards,
Alexey Kovyazin

IBSurgeon

среда, 15 декабря 2021 г. в 15:30:35 UTC+3, nick....@gmail.com:

Nick Upson

unread,

Dec 16, 2021, 4:12:16 AM12/16/21

to firebird...@googlegroups.com

yes, thanks everyone

the sweep fixed it, the cron job that does a regular sweep had been disabled

--

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/e4319482-d65d-4434-9035-52fe10108667n%40googlegroups.com.

Dimitry Sibiryakov

unread,

Dec 16, 2021, 5:33:16 AM12/16/21

to firebird...@googlegroups.com

Nick Upson wrote 16.12.2021 10:12:
> the sweep fixed it, the cron job that does a regular sweep had been disabled

That's why you should never turn autosweep off.

--
WBR, SD.

Reply all

Reply to author

Forward