Morning Raymond,

>> gfix -shut full -attach 0 <database>
> Still no luck in closing my database so that I can move it, etc...

What the above command does is to prevent any new attachments from being
allowed while it waits zero seconds to shut the database down cleanly.
If there are any attachments to the database after zero seconds, then
the above command will itself fail, and the database will remain open
and in use. You would (in Firebird 2.1 anyway) see something like the
following if the shut down fails:

lock conflick on no wait transaction
-database shutdown unsuccessful


The above command was a "polite" way to shut down. There is a less
polite way:

gfix -shut full -force 0 <database>

This kills any running transactions, prevents any new connections and
prevents new transactions from starting. It's not nice to your users to
do this though. However, it could be you have managed to get everyone
logged out and a rogue session is "stuck" - this option should get rid
of that!

> I tried this two different ways and was not successful in really "closing" the database
>
> gfix -shut full -attach 0<database>
> gfix -shut full -force 0<database>

There should be a space between the zero and the database name, I
presume the above is a type?

Did you check that the database was closed with:

gstat -header <database> | grep Attributes
Attributes full shutdown

> and the database still remained open (the date/time stamp was not updated)... due to an application that was connected to the database.

This is interesting as it means that the shutdown didn't work,
especially if you tried to force it closed. There is a bug in 2.0
whereby the -force option acts exactly like -attach - I can't remember
which version you said you were running. :-(

Also, I'm not sure which version fixed this problem.


Cheers,
Norm.

--
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
Thorpe House
61 Richardshaw Lane
Pudsey
West Yorkshire
United Kingdom
LS28 7EL

Company Number: 05132767