hello tilo, all!
now, is it correct that the approach is this: scan the output of backup_history_list for the last log id that was succefully imported. then identify all logbackup-files with an extension that is numerically higher than this and recover_start <medium> <extension of file> for each of them.If you end log restores in between individual log files with recover_cancel, it might be needed to reapply one or more log backups more than once. So if you use recover_cancel in your script, you should use the "Used LOG Page"-value of db_restartinfo and the 8-th and 9-th column of backup_history_list and backup_history_listnext to find the log backup needed for continuing the log restore. The "Used LOG Page"-value must be in the interval given of 8-th and 9-th column of backup_history_list/next.
this log recovery is giving me a headache... i now have a script that looks at backup_history_list of the importing host to determine which was the last log fragment that was successfully imported. then it looks at all available files and tries to insert them using recover_start. the reason for one-file-at-a-time is that i am doing this with dbmcli-calls in a simple shell script.
playing around with the dbmcli interactivly i get this impression:
look at db_restartinfo to find out what "Used Log Page" the instance currently is at. looking at all available files (medium_label xxx) find out, wich fragment has that page (might be at begin/end of a fragment or in between when recover_cancel was used).
even if one fragment ends with this page, recover_start from that fragment and treat -8020 as an ok to recover_replace the next fragment. continue with this with all the fragments you want to insert.
this seems to work, but i cannot stop. when i quit dbmcli (or use backup_cancel or recover_cancel) the kernel dies with "ERR 8 Admin ERROR 'cancelled' CAUSED EMERGENCY SHUTDOWN". db_restartinfo and the backup_history_list (after another backup_history_open) show that the log was successfully imported. question: how do i "commit" this backup session without going offline. i cant find a command for that in the 'help' output.
question: does that sound like it might be correct? is this actually scriptable? seems i need 'expect' or a more clever script for the complex dbmcli interaction.
isnt this supposed to be a standard problem? how do people do that? manually with the dbmgui?
thanks for your patience,
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 [EMAIL PROTECTED] 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/[EMAIL PROTECTED]
