Re: standby instance, log recovery

Heinrich, Tilo wrote:

hello Tilo!

> if it is like you say I'm surprised, that a simple 'util_execute clear log' did 
> not help. I should have asked for the output of db_restartinfo too.

exporting host:
Used LOG Page           659
First LOG Page          0
Restartable             1
Id Restart Record       (db-id of exporting host)
Id LOG Info             (db-id of exporting host)
Consistent              1

importing host:
Used LOG Page           611
First LOG Page          2147483647
Restartable             1
Id Restart Record       (db-id of importing host)
Id LOG Info             (db-id of importing host)
Consistent              1

hmm... the first log page looks strange...

> Given that data and log backups were created using the same database, you 
> should have no trouble restoring them in the new database, if you do not leave 
> state ADMIN between creation of the new database and restore of the backups.

well, this must be the point: i went online once after restoring the 
full backup in the importing host. it seems there is really no way to 
recover from the damage this does?

may i ask what's so dangerous about going online in the standby 
instance? is it that logs are being written? but the 'clear log' should 
help then? is it ok for the two systems to have different db-ids?

i will try again on monday with a new instance, not bringing that online 
accidentally. let's see what happens then.

thanks so far,
        Raimund

--
7. RedDot Anwendertagung der RedDot Usergroup e.V. am 31.1.2005
Pinuts präsentiert neue Entwicklung, http://www.pinuts.de/news

Pinuts media+science GmbH                 http://www.pinuts.de
Dipl.-Inform. Raimund Jacob               Raimund.Jacob@xxxxxxxxx
Krausenstr. 9-10                          voice : +49 30 59 00 90 322
10117 Berlin                              fax   : +49 30 59 00 90 390
Germany


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx