Subject RE: [ib-support] Gfix usage
Author Wilson, Fred
We do it (on NT4.0 and W2K systems), by using the net stop command to stop
the FB service, then save the service file and copy another one in it's
place that doesn't have the gds32 line in it, and, finally, restart the FB
service with the net start command. This insures that everyone is off (by
stopping the service), and that no one (there are no local applications that
run, only TCP/IP clients) can log into the database after it's restarted.
After the housekeeping stuff is finished, we reverse the process.

Best regards,
Fred Wilson
SE, Bell & Howell

-----Original Message-----
From: Paul Reeves [mailto:paul@...]
Sent: Tuesday, December 03, 2002 1:45 AM
Subject: Re: [ib-support] Gfix usage

A6-CMO Philippe Makowski wrote:

> In fact I want a procedure to be certain that I am the only one connected
> the database

There is no reliable and consistent way to achieve this at the moment.
The 'hack' is to try and rename the database file. If you can do that
then no-one is connected and you can then connect to the newly named
database and carry out whatever maintenance work is required.

The problem is that renaming a database will require some kind of access
to the file system that the database is stored on. This may not always
be possible.

I guess the proper solution to this is to ensure that when a database is
shutdown that only a single connection from either the owner or sysdba
is allowed. However, at the moment, multiple connections are allowed.


Paul Reeves
Supporting users of Firebird and InterBase

To unsubscribe from this group, send an email to:

Your use of Yahoo! Groups is subject to

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