On 25-4-2019 23:59, [email protected] [firebird-support] wrote: > I am sharing the gstat results for one of our databases below. Can > anyone please help on how far or close we are of reaching the > transaction counter limits of Firebird 2.5 please. > > Database header page information: > Flags 0 > Checksum 12345 > Generation 1035039622 > Page size 16384 > ODS version 11.2 > Oldest transaction 903227975 > Oldest active 1030787938 > Oldest snapshot 1030787938 > Next transaction 1031734200 > &n bsp; Bumped transaction 1 > Sequence number 0 > Next attachment ID 3277097 > Implementation ID 26 > Shadow count 0 > Page buffers 3000 > Next header page 0 > Database dialect 1 > Creation date Feb 1, 2018 12:05:29 > Attributes no reserve > > Thanks for any guidance.
Transaction ids in Firebird 2.5 and earlier are 32 bit signed integers, so the maximum value is 2^31 - 1 or 2,147,483,647. Your current next transaction is 1,031,734,200, so you have about 1,115,749,447 transactions left. Monitor the transaction count to determine the rate, and start planning a backup and restore of your database to reset the transaction count when you get near 2,000,000,000 based on that rate (or if the rate is very high, maybe even earlier). In Firebird 3 the transaction id was changed to a 48 bit unsigned integer (or max 281,474,976,710,656). So if you want more breathing room, consider upgrading to Firebird 3. Mark -- Mark Rotteveel
