Subject Re: [firebird-support] Re: Deadlock during index activation
Author Alec Swan
Not sure what you meant, but I don't see embedded 2.1.4 snapshot on
http://www.firebirdsql.org/download/snapshot_builds/win/2.1/

2010/7/29 Ismael L. Donis Garc´┐Ża <ismael@...>

>
>
> Because you not does try the embedded dll of the 2.1.4 snapshot
>
> Regards
> =========
> || ISMAEL ||
> =========
>
> ----- Original Message -----
> From: "Alec Swan" <alecswan@... <alecswan%40gmail.com>>
> To: <firebird-support@yahoogroups.com <firebird-support%40yahoogroups.com>
> >
> Sent: Thursday, July 29, 2010 3:04 PM
> Subject: Re: [firebird-support] Re: Deadlock during index activation
>
> > Sean,
> >
> > We have thousands of client applications using embedded Firebird 2.1.2
> and
> > one of the reported an index corruption problem which I describe in this
> > thread
> http://tech.groups.yahoo.com/group/firebird-support/message/109295
> >
> > The easiest way to fix corrupted index is to ACTIVATE it and that's what
> the
> > maintenance plan is doing. We could make the maintenance plan smarter and
> > only activate index if gfix reports it as broken, but that's just an
> > optimization. The bottom like is that we need to activate indexes to fix
> > index corruption.
> >
> > However, it's good to hear that you have success with your large
> deployment.
> > What version of Firebird are you using? Do you do any kind of maintenance
> on
> > your databases?
> >
> > Thanks,
> >
> > Alec
> >
> > On Thu, Jul 29, 2010 at 9:42 AM, Leyne, Sean <Sean@...<Sean%40broadviewsoftware.com>
> >wrote:
> >
> >>
> >>
> >> Alec,
> >>
> >>
> >> > Thank you for the explanation. Our application has a maintenance plan
> >> which
> >> > calls ACTIVATE INDEX on every index in the database. It is possible
> that
> >> other
> >> > queries and statements are run against the database during the
> >> maintenance
> >> > plan. According to your explanation those concurrent modifications may
> >> > cause the "deadlock" error to be thrown during index activation. Would
> >> you
> >> > suggest preventing concurrent queries and modifications during index
> >> > activation?
> >> >
> >> > Where can I get the full message for the "deadlock" error I am seeing?
> >> (What
> >> > I reported was the entire message I receive from Jaybird.)
> >>
> >> The have 100+ servers deployed at client locations (with databases
> between
> >> 1GB and 19GB in size) and we *never* need to perform index maintenance.
> >>
> >> I would suggest that the "maintenance" plan is over-thought.
> >>
> >> Sean
> >>
> >>
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
>
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > 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
> >
> >
> >
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]