Subject | Internal gds software consistency check (wrong record length (183)) |
---|---|
Author | Eric |
Post date | 2008-04-28T20:53:41Z |
Hi all,
Last week my database corrupted and users couldn't log in to the
database anymore.. The logfile displayed the following message:
NTUSBS (Server) Sat Apr 26 13:28:43 2008
Database: D:\NTU\DATABASE\POSITIE.IB
internal gds software consistency check (wrong record
length (183))
I'm working with Win2000 Small Bussiness Server, FireBird 1.5, and about
15 users logging in via Terminal Server.
Happily enough, GFix solved the problem this time and as far as I can
see I haven't lost any information
But my main concern is: What did (probably) cause this corruption??
Is there any knowledge about this, to avoid future problems??
Thanks in advance!
Eric Schokker
[Non-text portions of this message have been removed]
Last week my database corrupted and users couldn't log in to the
database anymore.. The logfile displayed the following message:
NTUSBS (Server) Sat Apr 26 13:28:43 2008
Database: D:\NTU\DATABASE\POSITIE.IB
internal gds software consistency check (wrong record
length (183))
I'm working with Win2000 Small Bussiness Server, FireBird 1.5, and about
15 users logging in via Terminal Server.
Happily enough, GFix solved the problem this time and as far as I can
see I haven't lost any information
But my main concern is: What did (probably) cause this corruption??
Is there any knowledge about this, to avoid future problems??
Thanks in advance!
Eric Schokker
[Non-text portions of this message have been removed]