Subject | Re: [firebird-support] Firebird problem |
---|---|
Author | Helen Borrie |
Post date | 2003-06-14T15:09:30Z |
At 10:29 PM 14/06/2003 +0800, you wrote:
is written to the database is also written to the shadow. So if a write
operation causes corruption to the database, the shadow will have the same
corruption.
The shadow can be activated when the disk containing the database fails, or
when the database is accidentally deleted. Don't use it on the assumption
that it will be a "good copy" of a corrupted database.
gfix -a /path/to/database/mydata.shd (Linux)
or
gfix -a drive:\path\to\database\mydata.shd (Windows).
For more info, see the chapter on Shadowing in the Operations Guide.
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_db_corr
heLen
>Hello,First -- be very clear that shadowing is not replication. Everything that
>1.How to operation that make the *.shd file automatic take over the main
>database when the main database cann't use?
is written to the database is also written to the shadow. So if a write
operation causes corruption to the database, the shadow will have the same
corruption.
The shadow can be activated when the disk containing the database fails, or
when the database is accidentally deleted. Don't use it on the assumption
that it will be a "good copy" of a corrupted database.
>I know the 'active', but I want to know the detail syntax by usingUse the command shell tool gfix. The syntax to activate the shadow is
>firebird1.0 server.
gfix -a /path/to/database/mydata.shd (Linux)
or
gfix -a drive:\path\to\database\mydata.shd (Windows).
For more info, see the chapter on Shadowing in the Operations Guide.
>2.What is the best method to maintenance appliction continuous runningYou need to repair the database. Instructions here:
>when the database file that includes page error can't been accessed.
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_db_corr
heLen