stevemilner_2000 wrote:

>
> Although the database doesn't seem to be suffering any problems in
> normal use; on a weekly basis gfix -v -full is reporting several
> errors with the central database, mainly with index page errors, some
> database page errors and the occasional record error.

Gfix actually reports several different types of error on the various
object types. Some are benign (e.g. orphan page) and others indicate a
potential catastrophe (e.g. wrong page type).

>
> host.domain.net Sun Jun 5 08:19:40 2005
> INET/inet_error: read errno = 110
> ....
> host.domain.net Mon Jun 6 19:28:59 2005
> SERVER/process_packet: broken port, server exiting
>

This suggests that a server process has crashed. The cause could be a
faulty UDF or ....? The crash could leave orphan pages and orphan back
versions.

>
> I have the following questions:
>
> Are the errors reported by gfix simply a consequence of the large and
> active database and should I schedule a backup and restore every week
> to resolve the problems?

You should send us a more complete description of the errors which will,
one hopes, give us a better chance of determining the cause and severity.

>
> Are the gfix errors related to the errors reported in the firebird log
> and if so what is the cause of these errors and how do I reduce or
> prevent these errors.

If, in fact, some server processes are crashing, it would be useful to
know which and why.

>
>

Regards,


Ann