Hello Fred, The actual problem is "RETURNCODE -7075", which means that the selected log backup does not match your data backup. Do you mind sending the files dbm.knl and dbm.ebf of the original database to this list?
Did you use "db_activate RECOVER ...", as Markus D�hr mentioned? Best regards, Tilo Heinrich SAP Labs Berlin -----Urspr�ngliche Nachricht----- Von: Claypool, Fred [mailto:[EMAIL PROTECTED] Gesendet: Montag, 14. M�rz 2005 18:11 An: [email protected] Betreff: SAP DB 7.4.3/33 Restore Problem Using HP's Data Protector 5.5 Hi there, I've been working with HP over the past few weeks to resolve an SAP DB 7.4.3/33 restore problem. I'm using the external backup tool Data Protector 5.5. I'm trying to perform a test migration by restoring a full backup from server A to server B (which appears to work fine), followed by a restore of the logs from server A to server B. It's this last part that appears to fail. After about an hour of clearing logs (util_execute clear log), the actual log restore runs (recover_start) and appears to finish (according to DP) a few minutes later. However, I believe SAP DB is killing some process along the way which is causing the whole restore to fail. If you all see anything unusual in the trace files below that might explain what's going on, please let me know. Thanks, ~Fred My latest dbahist file includes the following lines of interest: ------------------------------------------------------------------------ --------------------------- 2005-03-14 09:58:16 The backup tool process has finished work with return code 0. Asking for state of database. Got the following reply from db-kernel: SQL-Code :0 Redo Transactions Read:0 Redo Transactions Done:0 2005-03-14 09:58:18 The database is working on the request. 2005-03-14 09:58:28 The database is working on the request. 2005-03-14 09:58:44 The database is working on the request. 2005-03-14 09:59:03 The database is working on the request. 2005-03-14 09:59:18 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK. 2005-03-14 09:59:20 The database is working on the request. 2005-03-14 09:59:30 The database is working on the request. 2005-03-14 09:59:45 The database is working on the request. 2005-03-14 09:59:50 The database is working on the request. The restore operation has ended. 2005-03-14 09:59:50 Filling reply buffer. Have encountered error -24920: A cancel of the database request failed. The backup tool ended with 0 as sum of exit codes. Constructed the following reply: ERR -24920,ERR_BACKUPOP: backup operation was unsuccessful A cancel of the database request failed. The backup tool ended with 0 as sum of exit codes. Reply buffer filled. ------------------------------------------------------------------------ --------------------------- My dbm.prt file includes the following lines of interest: ------------------------------------------------------------------------ --------------------------- 2005-03-14 09:51:59 0x00006791 0 DBM command recover_start BACKDP-Archive LOG ExternalBackupID "DEV 0503091:1 Stream" 2005-03-14 09:59:52 0x00006791 ERR -24920 DBM ERR_BACKUPOP: backup operation was unsuccessful 0x00006791 ERR -24920 DBM A cancel of the database request failed. The backup tool ended with 0 as sum of exit codes. ------------------------------------------------------------------------ --------------------------- My dbm.utl file includes the following lines of interest: ------------------------------------------------------------------------ --------------------------- 2005-03-14 08:58:20 4235987C0004 0000 CLR CLEAR LOG 2005-03-14 09:51:58 4235987C0004 0001 RET RETURNCODE 0 2005-03-14 09:52:00 4235A5100006 0000 RLG RESTORE LOG QUICK FROM '/var/opt/omni/tmp/DEV.BACKDP-Archive.1' PIPE MEDIANAME 'BACKDP-Archive' 2005-03-14 10:01:58 4235A5100006 0001 RET RETURNCODE -7075 2005-03-14 10:01:58 4235A5100006 0002 TAP DATE..............^A-^NM-O-@ 2005-03-14 10:01:58 4235A5100006 0003 TAP TIME.............. ar:/o:pt 2005-03-14 10:01:58 4235A5100006 0004 TAP SERVERDB.......... omni/tmp/DEV.BACKD 2005-03-14 10:01:58 4235A5100006 0005 TAP SERVERNODE........ -Archive.1 2005-03-14 10:01:58 4235A5100006 0006 TAP KERNEL VERSION.... 2005-03-14 10:01:58 4235A5100006 0007 TAP PAGES TRANSFERRED. *********** 2005-03-14 10:01:58 4235A5100006 0008 TAP PAGES LEFT........ *********** 2005-03-14 10:01:58 4235A5100006 0009 TAP NO OF VOLUMES..... *********** 2005-03-14 10:01:58 4235A5100006 000A TAP MEDIA NAME........ 2005-03-14 10:01:58 4235A5100006 000B TAP TAPE NAME......... 2005-03-14 10:01:58 4235A5100006 000C TAP TAPE ERRORTEXT.... 2005-03-14 10:01:58 4235A5100006 000D TAP TAPE LABEL........ 2005-03-14 10:01:58 4235A5100006 000E TAP IS CONSISTENT..... TRUE 2005-03-14 10:01:58 4235A5100006 000F TAP FIRST LPNO........ *********** 2005-03-14 10:01:58 4235A5100006 0010 TAP LAST LPNO......... *********** 2005-03-14 10:01:58 4235A5100006 0011 TAP DBSTAMP1 DATE..... - - 2005-03-14 10:01:58 4235A5100006 0012 TAP DBSTAMP1 TIME..... : : 2005-03-14 10:01:58 4235A5100006 0013 TAP DBSTAMP2 DATE..... - - 2005-03-14 10:01:58 4235A5100006 0014 TAP DBSTAMP2 TIME..... : : 2005-03-14 10:01:58 4235A5100006 0015 TAP BD PAGE COUNT..... *********** 2005-03-14 10:01:58 4235A5100006 0016 TAP TAPEDEVICES USED.. *********** 2005-03-14 10:01:58 4235A5100006 0017 TAP DB_IDENT.......... 2005-03-14 10:01:58 4235A5100006 0018 TAP MAX USED DATA PNO. *********** ------------------------------------------------------------------------ --------------------------- Finally, my knldiag includes the following lines of interest: ------------------------------------------------------------------------ --------------------------- 2005-03-14 09:56:55 267 11597 IO Open '/var/opt/omni/tmp/DEV.BACKDP-Archive.1' successfull, fd: 121 2005-03-14 09:56:55 11 52012 RESTORE error occured, basis_err 4306 2005-03-14 09:59:19 7 11577 COMMUNIC Cancel request for T118 2005-03-14 10:00:05 6 WNG 11840 COMMUNIC Killing T118 for died apid 26513 ------------------------------------------------------------------------ --------------------------- -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
