Subject | Re: [firebird-support] Terminated abnormally (4294967295) |
---|---|
Author | Helen Borrie |
Post date | 2004-04-03T08:26:42Z |
At 09:47 AM 3/04/2004 +0200, you wrote:
code (and it's not)..and it's not a prime number (which it clearly isn't),
it does happen to be a number which is 1 higher than the largest number you
can store in an unsigned 4-byte integer. The transaction ID (an unsigned
4-byte integer) in a database rolls over at this point; also any
generators that came through in an ODS9 database would be 32-bit, not 64-bit.
How long is it since you backed up and restored those IB databases (the
ones that are not your main dbs)?
Have you examined all your generators to see whether some are
overflowing? You would get an overflow if your app or a trigger tried to
increment a Dialect 3 generator to fill an integer (32-bit) though I think
that overflow would have occurred at 2147483647 because of signing.
Have you done a gstat -h on each database to see what the Next Transaction
would be?
/heLen
>Hi,Nils, some more number facts. Given that the number above isn't an error
>
>we use FB 1.5 on Windows NT 4.0 (SVP 6). This System have 2 Processors
>(PIII) and 512 RAM. Firebird are assigned to processor 2.
>
>Since switsching to FB 1.5 we have 3 - 4 times that the FBServer process
>will be terminated with the following error message:
>
> Terminated abnormally (4294967295)
>
>We use Firebird as DB Server for our content managment system and
>serveral other databases... The two main databases have a size with more
>then 500/700 MB.
>
>* The two main databases are backuped/restored unter FB 1.5.
>* Some other Databases are still in IB 6 Format.
>
>Is there a solution for this problem?
code (and it's not)..and it's not a prime number (which it clearly isn't),
it does happen to be a number which is 1 higher than the largest number you
can store in an unsigned 4-byte integer. The transaction ID (an unsigned
4-byte integer) in a database rolls over at this point; also any
generators that came through in an ODS9 database would be 32-bit, not 64-bit.
How long is it since you backed up and restored those IB databases (the
ones that are not your main dbs)?
Have you examined all your generators to see whether some are
overflowing? You would get an overflow if your app or a trigger tried to
increment a Dialect 3 generator to fill an integer (32-bit) though I think
that overflow would have occurred at 2147483647 because of signing.
Have you done a gstat -h on each database to see what the Next Transaction
would be?
/heLen