Hi Steffen,

> In an older mail to this list (2010-10-01 09:28) Norman Dunbar wrote:
>
>> Note, if gfix hasn't been used against this database, then the above
> command will not display "Attributes".
>
> So does the absence of that line in the output say "gfix was not used, so no
> information" or does is say "forced writes is off" ?

On a database that has never been "gfix -write async" the Attributes do
not show anything for forced writes. At least, up until version 2.5
where it *does* show "forced writes" immediately after a database has
been created.

On 2.1.3, there is nothing listed until after you run "gfix -write" to
set the forced writes on.

Once the database has had "gfix -write" run against it, the attributes
do show details.

There may have been a change between 2.1.3 and 2.5 where this was resolved.


Cheers,
Norman.

>
>
> My problem: This database is part of one of our products and I need to be
> sure, it always works in forced writes mode.
> I always thought it would, but now I want to be sure.
>
> Your statement above indicated, we are wrong, but what now?
>
> Can we "simply" run " gfix -user sysdba -pass XYZ -write sync
> /path/to/database.fdb" ?
>
> What about backups? If they are restored, do we need to run that command
> again?
>
>
> Regards,
> Steffen
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>
>

--
Norman Dunbar
Dunbar IT Consultants Ltd

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

Company Number: 05132767