On Wed, 23 Jan 2013 16:13:07 -0000, "patrick_marten"
<patrick_marten@...> wrote:

> Hello,
>
> since a few days I've noticed a problem in my application, when doing

some

> database updates.
>
> What I'm doing:
> 1. Shutdown database with
> "D:\My Application\gfix.exe" -shut full -force 0 -user SYSDBA -pas
> masterkey "C:\Users\Public\Documents\MyDatabase.FDB"
>
> 2. Doing some updates
>
> 3. Back & Restore of the database
>
> 4. Restart database with
> "D:\My Application\gfix.exe" -online -user SYSDBA -pas masterkey
> "C:\Users\Public\Documents\MyDatabase.FDB"
>
> This has worked all the time (like 2 years), but suddenly it doesn't
> anymore - can't say that I've changed something...

What doesn't work? Do you get an error message, if so: what is the error
message

> One version of my application ships with FB 2.1.4, the new one with FB
> 2.5.2. For the first one it seems to be enough to introduce some delay
> between the processes, for the second one it doesn't work.
>
> The article
>

http://www.firebirdsql.org/file/documentation/reference_manuals/user_manuals/html/gfix-dbstartstop.html

> says that using "full" is not an acceptable option for starting up a
> database, so I've also tried to shutdown the database using "single"
> instead, but it didn't change anything.

That document tries to convey that "gfix -shut full" is acceptable, while
"gfix -online full" isn't, as that doesn't make sense for online.

Mark