Here is the doc link I am referring to: http://dev.mysql.com/doc/maxdb/en/88/c290d224d9e140a9c7048ffff0c233/content. htm
If sdbinst can do the migration then why not use the very same logic to allow the dbmgui to migrate 7.3 images to a 7.5 server? -----Original Message----- From: Kevin Wilson Sent: Monday, June 07, 2004 12:06 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: DBMGUI v7.5.00.11 & 7.4.3.30 fail to ... You have GOT to be joking! Everything in the docs state that an image newer than 7.3.0.25 can be migrated. 2004-06-07 09:20:36 7930 ERR 52000 RESTORE Kernel 7.3.0 Build 046-000-094-452 2004-06-07 09:20:36 7930 ERR 52000 RESTORE Restore not possible. Hostfile too old! 2004-06-07 09:20:36 7929 ERR 52012 RESTORE error occured, basis_err 1040 -----Original Message----- From: Strahl, Torsten [mailto:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 10:01 AM To: Kevin Wilson Cc: Open Source List Subject: AW: DBMGUI v7.5.00.11 & 7.4.3.30 fail to ... Hi Kevin, you send me the knldiag of the failed recovery attempt? Regards, Torsten SAP DB, SAP Labs Berlin -----Urspr�ngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Montag, 7. Juni 2004 16:49 An: [EMAIL PROTECTED] Betreff: DBMGUI v7.5.00.11 & 7.4.3.30 fail to ... migrate a 7.3.0.46 migration backup to a clean install MaxDB 7.5.0.14 server installation. I have migrated instances before using the dbmgui so I do know the process. The error given is: -24988 sql error [db_activate RECOVER <image name> DATA]; -111, incompatible incremental backup Here is the link which states the dbmgui has a bug that prevents the migration but this was reported way back in Feburary so why wouldn't the latest post of the 7.5 series dbmgui include the fix? http://www.mail-archive.com/[EMAIL PROTECTED]/msg02096.html Thanks, Kevin
