At 09:46 AM 05-09-01 +0300, you wrote:

>Thank you very much. I knew about those limitations, but didn't realize that
>they're causing my problems here. I'm running some tests here in our
>research lab, and very often I'm getting IB database corruptions. You
>mentioned that it'll get corrupted as soon as it gets 2/4 Gbs big... It
>seems that that's what I'm observing.
>
>Can you tell me something: very often in my test I get the following
>message:
>
>GDS Software consistensy check - can't continue after bug check
>
>...
>and also:
>Database file appears corrupt.
>
>Can you tell me what do those errors mean and how is it possible for them to
>happen?

Write errors in the operating system or hardware are the usual cause, resulting in broken or lost database structures (pages, indexes, etc.) When these structures get corrupted, it can cause committed data to be unrecoverable.

Needless to say, if your OS is overwriting structures because your file size has gone over the limit, this is an EXTREME condition that guarantees write errors as long as it is still possible to connect to the database!

>Also, in another note that I posted a few minutes ago, I'm asking
>whether it's possible to validate the database from withih my application,
>so that I can detect the above states BEFORE they actually happen after a
>query execution. Can you give me a hint?

Database validation requires exclusive access to the database. It's hard to see how pre- or post-query validation could be practicable in a multi-user environment..but I *think* the latest release of Firebird does test for file size and won't allow connection if the file is too large.

Claudio, Mark, Sean - please confirm this.

rgds,
Helen



All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________