[firebird-support] Re: Trace cause of performance drop
Firebird version is: WI-V6.3.2.26540 Firebird 2.5 I am not very familiar with working with the Trace API at all at this point. So this will be a later task, should I not be able to locate the problem here. Unless you have a suggestion here? Michael
Re: [firebird-support] Re: Trace cause of performance drop
On 16 Dec 2014 00:30:18 -0800, "michael.vilhelm...@microcom.dk [firebird-support]" wrote: > Firebird version is: WI-V6.3.2.26540 Firebird 2.5 That is not actually a Firebird version; that is a version reported through an old API call for Interbase compatibility. However build number 26540 suggests it is Firebird 2.5.2. > I am not very familiar with working with the Trace API at all at this > point. So this will be a later task, should I not be able to locate the > problem here. > Unless you have a suggestion here? My first suggestion would be to upgrade to 2.5.3 Update 1 and backup and restore your database. Mark
Re: [firebird-support] Re: Trace cause of performance drop
I stand corrected :) Version is 2.5.2.26540. We have planned an update to the newest Firebird version december 25. This database runs live and due to the christmas shopping users are online from 6 to 23.30.And the database must not be unavailable. So - we will wait. Backup / Restore has been done recently, and we have another planed medio january. Sinse the database is almost 100Gb this takes 85 minutes to dump and almost 480 minutes to restore. So we have to have a bigger window as we have right now. This customer has 3 shops in Copenhagen airport. Therefore they are online every day from 6 to at least 22. Mivi
Re: [firebird-support] Re: Trace cause of performance drop
2014-12-16 9:39 GMT+01:00 Mark Rotteveel m...@lawinegevaar.nl [firebird-support] : > > My first suggestion would be to upgrade to 2.5.3 Update 1 and backup and > restore your database. > Why is needed to backup + restore the database when upgrade to 2.5.3. As I know is only necessary to avoid lock conversion denied. Is there anything else?
Re: [firebird-support] Re: Trace cause of performance drop
On Tue, 16 Dec 2014 12:00:45 +0100, "Jesus Garcia jeg...@gmail.com [firebird-support]" wrote: > 2014-12-16 9:39 GMT+01:00 Mark Rotteveel m...@lawinegevaar.nl > [firebird-support] : >> >> My first suggestion would be to upgrade to 2.5.3 Update 1 and backup and >> restore your database. >> > Why is needed to backup + restore the database when upgrade to 2.5.3. As I > know is only necessary to avoid lock conversion denied. Is there anything > else? I don't know the history of this DB, for all I know it was created with 2.5.1 and suffers from the index bug. Also given the described problem, recreating the database (what a restore does) might solve it as well. I admit it is an easy answer to what might be a complex problem. Mark
