--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> No, you can "shut down" a database in the sense that you take the

database

> off-line, preventing all users except sysdba or the database owner

from

> connecting. To understand how it works, you should read Ch. 39 of

The

> Firebird Book (if you have it); otherwise Google for OpGuide.pdf,

download

> it, and look up the details of gfix -shut. If you try to guess

this one,

> or to go by FAQ notes attached to some third party tool, you're

fairly

> unlikely to get it to work.

Someone here happened to have the book, so I risked a hernia ;-),
carried it back to my office and read through Ch. 39.

I am sitting at my C:\Program Files\Firebird\Firebird_1_5
directory. My first attempt was:

bin\gfix -shut -at 0 test.gdb
Your user name and password are not defined. Ask your database
administrator to set up a Firebird login.

On page 836 it said I could do this for a local connection, so I did:

SET ISC_USER=SYSDBA
SET ISC_USER=masterkey

Then I ran the command again and I guess it worked. There was no
error message, at least.

1. Is there a command I could run that would visually confirm that I
now have exclusive access?

2. In parallel, I'm trying to figure out how to run a Hibernate
tool, SchemaExport, which should generate a DDL file containing
commands to set up tables based on the Hibernate mapping files in
their example. I'm hoping I can then manually send that DDL file to
Firebird, and that the rest of the code in the Hibernate example
will then work. To send the DDL file, would I do this:

bin\isql.exe test.gdb -u sysdba -p masterkey -i foo.sql
(where foo.sql is the hibernate-generated DDL file)

Thanks,
-Jeff