Morning Christian,

>> I have installed and started a production database with
>> "forced write = off", and have now set "forced write=ON".
>>
>> Is this setting active immediately or are some actions required

It's immediate. You can check using gstat -h, as per the following:

tux> gstat employee | grep -i attributes
Attributes

Note, if gfix hasn't been used against this database, then the above
command will not display "Attributes".


tux> gfix employee -write sync
tux> gstat employee | grep -i attributes
Attributes force write

tux> gfix employee -write async
tux> gstat employee | grep -i attributes
Attributes


HTH

Cheers,
Norman.



Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.

If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk