Hi all,

After a great help from IBSurgeon support, i found that the problem
was related to database "on connect" triggers and corrupt indices.

A corrupt index, which was used during an "on connect" trigger, was
causing the segmentation fault and corrupting my database.

The solution proposed by IBSurgeon support was to access database
ignoring database triggers (isql -nodbtriggers <database>) and disable
the database triggers inside. It worked perfectly (i still had to
repair the database using FBFirstAID).

Regards,

Fabiano

On Sat, Apr 25, 2009 at 12:52 PM, personalsoft_fabiano
<fabiano@...> wrote:

> Hi all,
>
> I´m having problems with a corrupt database.
>
> Here is what is happening in the server:
>
> root@server1:/temp# gbak -b -v database.fdb database.fbk
> Segmentation fault
>
> No messages in firebird.log
>
> I did a copy to my local computer, repaired it with FBFirstAID (after repair it fix all erros, and shows all relations and pages OK), and when i try to backup, verify, mend or connect to it, i get:
>
> MICRO-FABIANO-2 (Client)        Sat Apr 25 12:33:31 2009
>        XNET error: Server shutdown detected
>
> No way to connect to database.
>
> Do someone have another idea of what should i try?
>
> Regards,
>
> Fabiano
>
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu.  Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>
>