Subject is corrupted (or not)
Author Aage Johansen
A couple of developers made some (unspecified) changes to some databases,
some errors appeared in the log - and some days later the server terminated
itself. Any connection between the incidents?

Messages were like this:
-----------------------
KRG_SRV9 (Server) Tue Nov 15 14:35:09 2005
Database E:\PROSJEKTER\LOG_PROJ.FDB
RDB$FLAGS for trigger CHECK_3 in RDB$TRIGGERS is corrupted (304)

KRG_SRV9 (Server) Tue Nov 15 14:35:09 2005
Database E:\PROSJEKTER\LOG_PROJ.FDB
RDB$FLAGS for trigger CHECK_4 in RDB$TRIGGERS is corrupted (304)
-----------------------
This pair appeared 3 times, then once more some seconds later, and then
twice more.
Some hours later, similar messages from another database appeared, and
again the next day.
I think the developer(s) worked late, and never checked the log. And, why
would they?
They said they were just doing "innocent" changes - users, rights, maybe a
new table. Probably, no other connections to the databases existed (they
might have more than one open themselves, however).

5 days later fbserver.exe "terminated abnormally" - there were no other
messages.
The version is WI-V6.3.2.4731, ODS 10.1.


Is Fb/1.5 more likely to find/see errors (and terminate) than earlier versions?
The nightly backup did not see any errors (at least nothing was written to
the log).


btw: "Tue Nov 15 14:35:09 2005"
Is this a nutty way to format a timestamp, or what?


--
Aage J.