OK, but that just goes to show that Database Manager GUI does some unwanted things behind the scenes (in this case, activating the database before I want to activate it). That's why I suggested to explore the scripts solution first.
Eduard On 1/22/07, Brunzema, Martin <[EMAIL PROTECTED]> wrote:
> -----Original Message----- > From: Eduard M [mailto:[EMAIL PROTECTED] > Sent: Monday, January 22, 2007 3:30 PM > To: Brunzema, Martin > Cc: maxdb@lists.mysql.com > Subject: Re: I/O error trying to recover log backup > > Martin, > > Now, as you advised, I created database for restore thru > Database Manager > GUI. I didn't restore data backup thru GUI. Then I restore > data backup using > command line client. Next, when I try to restore log backup, > I get this > error: > > dbmcli on STANDBY>recover_start burvlog LOG > ERR > -24988,ERR_SQL: SQL error > -9407,System error: unexpected error > 3,Database state: OFFLINE > 20040,Logrecovery is not allowed, because state of log volume is > 'HistoryLost' (log must be cleared) > 8,Log- and Data are not compatible because 'Restore Log with Log State > 'HistoryLost' is not allowed'. > 20028,Initialization of log for 'restore log' failed with > 'LogAndDataIncompatible' Hi Eduard, you get this error if the database had been online before restoring the log. Maybe there is some conrent of a previous try in the logvolume, which prevents now a recovery. You can intialize the logvolume in admin mode with the command util_execute clear log But be careful: Any data on the logvolume will be lost forever. Kind regards, Martin
