Subject | Re: [firebird-support] Very strange behavior |
---|---|
Author | Helen Borrie |
Post date | 2006-03-14T02:16:33Z |
At 12:55 PM 14/03/2006, Marco Castro wrote:
1. The database had been set to disable synchronous write, i.e.
Forced Writes off.
2. The pumping of the data had occurred in several contiguous
scripts (through use of the INPUT command, in a single transaction.
3. During the running of the script, the database file had been
subjected to a system backup that did not honor the exclusive lock
that the server had on the database file.
./heLen
>Hello,Yes, I do recall a report of such a thing. The factors in this case were:
>
> Did anybody got a situation when a database is populated and
>commited and after restarting the server the data is lost? I mean,
>everything comes to the initial status. Including counters. A client
>has got this behavior 4 times.
1. The database had been set to disable synchronous write, i.e.
Forced Writes off.
2. The pumping of the data had occurred in several contiguous
scripts (through use of the INPUT command, in a single transaction.
3. During the running of the script, the database file had been
subjected to a system backup that did not honor the exclusive lock
that the server had on the database file.
./heLen