Re: [firebird-support] Hiow to corrupt a Firebird database

2012-01-18 Thread Alexandre Benson Smith
Hi !

Em 17/1/2012 09:44, Maya Opperman escreveu:
> Hi,
>
> I was under the impression that copying a database that is currently in use 
> can cause a corruption because windows xcopy might deny the Firebird server 
> access to that file momentarily. I was looking for an official statement on 
> this for a customer of mine and found this:
>
> http://www.firebirdsql.org/manual/qsg10-howtocorrupt.html
>
> but it doesn't include the copying/zipping of a live database. Is the 
> documentation out of date, or is it not an issue any more?

If it doen't corrupt the database because of some kind of locking it 
will almost certainly generate a corrupted copy, because the pages 
already copied could be modified to point to pages at the end of the 
file... Copying a live databse IS NOT an option... If you wish to copy, 
you should first lock the database using NBAK. Read NBAK docs to know 
more about it.

or

use gbak to "dump" the database contents to a back-up file.

> Regards
> Maya
>
> PS. Similarly, in the past, I have also been advise to keep connection 
> strings exactly the same from all client connections, but I can't see 
> anything on that either

It was an issue on earlier versions of FB, don't recall when it was 
"fixed" but if you use 1.5 or later I don't think you will have any kind 
of problem...

see you !



RE: [firebird-support] Hiow to corrupt a Firebird database

2012-01-17 Thread Maya Opperman
>> I was under the impression that copying a database that is currently 
>> in use can cause a corruption because windows xcopy might deny the 
>> Firebird server access to that file momentarily. I was looking for an 
>> official statement on this for a customer of mine and found this:

>> http://www.firebirdsql.org/manual/qsg10-howtocorrupt.html

>> but it doesn't include the copying/zipping of a live database. Is the 
>> documentation out of date, or is it not an issue any more?

>Not everything is listed there.
>More details can be found here: "Firebird and InterBase corruptions reasons" 
>http://ib-aid.com/articles/item70


Oooo, lovely, thanks!



Re: [firebird-support] Hiow to corrupt a Firebird database

2012-01-17 Thread Thomas Steinmaurer
> I was under the impression that copying a database that is currently in use 
> can cause a corruption because windows xcopy might deny the Firebird server 
> access to that file momentarily. I was looking for an official statement on 
> this for a customer of mine and found this:
>
> http://www.firebirdsql.org/manual/qsg10-howtocorrupt.html
>
> but it doesn't include the copying/zipping of a live database. Is the 
> documentation out of date, or is it not an issue any more?

Others have replied on that already.

> Regards
> Maya
>
> PS. Similarly, in the past, I have also been advise to keep connection 
> strings exactly the same from all client connections, but I can't see 
> anything on that either

AFAIR, this was an issue in InterBase 6 (or even pre V6?) which has been 
fixed in Firebird 1.0.



-- 
With regards,
Thomas Steinmaurer (^TS^)
Firebird Technology Evangelist

http://www.upscene.com/
http://www.firebirdsql.org/en/firebird-foundation/


Re: [firebird-support] Hiow to corrupt a Firebird database

2012-01-17 Thread Alexey Kovyazin
Hello Maya,

Not everything is listed there.
More details can be found here: "Firebird and InterBase corruptions 
reasons" http://ib-aid.com/articles/item70

Regards,
Alexey Kovyazin
IBSurgeon





> Hi,
>
> I was under the impression that copying a database that is currently 
> in use can cause a corruption because windows xcopy might deny the 
> Firebird server access to that file momentarily. I was looking for an 
> official statement on this for a customer of mine and found this:
>
> http://www.firebirdsql.org/manual/qsg10-howtocorrupt.html
>
> but it doesn't include the copying/zipping of a live database. Is the 
> documentation out of date, or is it not an issue any more?
>
> Regards
> Maya
>
> PS. Similarly, in the past, I have also been advise to keep connection 
> strings exactly the same from all client connections, but I can't see 
> anything on that either
>
> [Non-text portions of this message have been removed]
>
> 



[Non-text portions of this message have been removed]



Re: [firebird-support] Hiow to corrupt a Firebird database

2012-01-17 Thread Mark Rotteveel
On Tue, 17 Jan 2012 11:44:53 +, Maya Opperman

wrote:
> Hi,
> 
> I was under the impression that copying a database that is currently in
> use can cause a corruption because windows xcopy might deny the Firebird
> server access to that file momentarily. I was looking for an official
> statement on this for a customer of mine and found this:
> 
> http://www.firebirdsql.org/manual/qsg10-howtocorrupt.html
> 
> but it doesn't include the copying/zipping of a live database. Is the
> documentation out of date, or is it not an issue any more?
> 
> Regards
> Maya
> 
> PS. Similarly, in the past, I have also been advise to keep connection
> strings exactly the same from all client connections, but I can't see
> anything on that either

I actually believe (but I am not sure) it is not the original database
that you can corrupt this way, but the copy is very likely to get corrupted
as it will have an inconsistent view of the database content. I do not
think that the (x)copy locks the file when performing the copy.

Mark


[firebird-support] Hiow to corrupt a Firebird database

2012-01-17 Thread Maya Opperman
Hi,

I was under the impression that copying a database that is currently in use can 
cause a corruption because windows xcopy might deny the Firebird server access 
to that file momentarily. I was looking for an official statement on this for a 
customer of mine and found this:

http://www.firebirdsql.org/manual/qsg10-howtocorrupt.html

but it doesn't include the copying/zipping of a live database. Is the 
documentation out of date, or is it not an issue any more?

Regards
Maya

PS. Similarly, in the past, I have also been advise to keep connection strings 
exactly the same from all client connections, but I can't see anything on that 
either



[Non-text portions of this message have been removed]