>the problem is, that you didn't succeed in making a >Log-Backup 002 (otherwise one could see the corresponing >entry in the file dbm.knl).
I was able to create the backup (autosave.002) before dropping my database, I used DBM GUI to create a log backup using the autolog device (auto) and it created the file. The traces I did send correspond to the new instance I recreated, not to the old one. Regards, Martin ----- Original Message ----- From: "Brunzema, Martin" <[EMAIL PROTECTED]> To: "'Martin Cordova S.'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, June 23, 2003 12:50 PM Subject: AW: -71,connection broken - error restoring data + log... > -----Urspr�ngliche Nachricht----- > Von: Martin Cordova S. [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 23. Juni 2003 18:32 > An: [EMAIL PROTECTED] > Betreff: -71,connection broken - error restoring data + log... > > > Hi, I receive this error when trying to restore my last autolog file: > > >recover_start auto LOG 002 > ERR > -24988,ERR_SQL: sql error > -71,connection broken > > Below you will see my dbm.knl, dbm.prt, and kernel traces. I > am able to > restore my data backup, but I cannot recover my last data > from autosave.002. > Any help will be very appreciated. Thanks. Martin. > > 1) My Scenario: > > I re-created my database instance to simulate a total crash, > I used the same > script that was run to create it. Before dropping my database > to simulate > the crash, I executed a full data backup, added some more > data, and then > executed a log backup, which created another autosave.002 > file (using DBM > GUI). This is my creation script: > SNIP > > 2) My recover script: > > db_admin > util_connect dbm,dbm > util_execute init config > recover_start data DATA > recover_start auto LOG 002 > util_release > db_online > > 4) DBM.KNL > > 3EF726780002| |HISTLOST | | |2003-06-23 12:10:32| | | | | | | | 0| | > 3EF726900004|DAT_00001|SAVE WARM|2003-06-23 12:10:56|2003-06-23 > 12:10:56|2003-06-23 12:10:57|2003-06-23 12:10:58| 1005| |NO > |data | 224| 1| > 0| | > 3EF726920006|LOG_00001|SAVE WARM|2003-06-23 12:10:39|2003-06-23 > 12:10:54|2003-06-23 12:10:58|2003-06-23 12:11:00| 0| 971| > |auto | 352| 1| 0| > | > 3EF728060002| |HISTLOST | | |2003-06-23 12:17:10| | | | | | | | 0| | > 3EF728070003|DAT_00005|RESTORE |2003-06-18 10:51:11|2003-06-18 > 10:51:11|2003-06-23 12:17:11|2003-06-23 12:17:13| 14401| |NO > |data | 296| 1| > 0| | Hi, the problem is, that you didn't succeed in making a Log-Backup 002 (otherwise one could see the corresponing entry in the file dbm.knl). This leads to an open-error during the "recover_start auto LOG 002", which causes a kernel-shutdown. This is solved in 7.4.3 Build 23 with PTS# 1121681 regards, Martin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
