Martin,
This does not work for me because my whole point of database restore is to
create a standby instance, recover it once from data backup and then
incrementally restore log backups. I want to activate it only in case of a
hardware error on master instance. I understand that once I activate it, I
won't be able to restore any more log backups into it.
Any other suggestions?
Eduard
On 1/22/07, Brunzema, Martin <[EMAIL PROTECTED]> wrote:
From: Eduard M [mailto:[EMAIL PROTECTED]
Sent: Monday, January 22, 2007 4:36 PM
To: Brunzema, Martin
Cc: maxdb@lists.mysql.com
Subject: Re: I/O error trying to recover log backup
Hi Martin,
Maybe let us continue with trying to solve this using command
line, since using DB Manager GUI introduces another possibility of
errors (i.e. I don't the commands that it is executing behind the
scenes). So the question is: I create standby using the scripts below.
Why is log volume (LOG_001) not being created? This is probably the
cause of this error that I mentioned:
... [stuff deleted]
echo "recover database"
_o=`cat <<EOF | dbmcli -uUTL -d $DB_DATABASE -u dbm,dbm 2>&1
recover_start burvis
recover_start burvlog LOG 001
... [stuff deleted]
Hi Eduard,
you did't activate the database. Instad of just
recovering your databackup you should use the command
db_activate RECOVER burvis
Once you have activated a database, it is sufficient
to only recover data.
Kind regards, Martin
