Subject | Re: FBKs being left open |
---|---|
Author | Steve Harp |
Post date | 2006-04-18T22:35:32Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
a single user application and everything is on the local machine. The
Firebird service runs locally and the application is local.
Transactions in the application are set to AutoCommit. Out of the
800+ locations running this application, we're seeing about 10-15
support calls a week related to this problem. The calls appear to be
random and I can't tie it to any one OS or customer's setup. However,
the culprit is always a FBK that is open when we try to delete it or
rename it.
Steve
>I'm sorry Helen. I don't understand your question. This is basically
> At 12:55 AM 19/04/2006, you wrote:
> >Hi All,
> >
> >I have an application which is running in over 800 restaurants and
> >uses Firebird v1.52. During backups, I use a TIBOBackupService to
> >create an fbk and this fbk is stored in a zip file.
> >
> >When restoring, the first step is to delete any fbk files that exist
> >before trying to restore the zip. Sometimes, this deletion fails
> >because the fbk is open. If I didn't delete the file, the restore of
> >the zip would fail for the same reason. The only solution we've found
> >when this happens is to restart the Firebird Guardian. However, in
> >the restaurants, the users don't have adequate rights to restart a
> >service.
> >
> >This doesn't always happen but it's generating a large number of
> >support calls. Hense, my customer is blaming Firebird and me for
> >using Firebird.
> >
> >Has anyone else seen this problem? If so, how did you deal with it?
>
> Are there specific deployment conditions at the problem sites, where
> you are trying to run the backup from the same application space as
> the main app and/or the main app is using a Windows local connection?
a single user application and everything is on the local machine. The
Firebird service runs locally and the application is local.
Transactions in the application are set to AutoCommit. Out of the
800+ locations running this application, we're seeing about 10-15
support calls a week related to this problem. The calls appear to be
random and I can't tie it to any one OS or customer's setup. However,
the culprit is always a FBK that is open when we try to delete it or
rename it.
Steve