> >> -----Original Message-----
> >> From: Hans Scheffers [mailto:[EMAIL PROTECTED]]
> >> Sent: Dienstag, 18. Februar 2003 15:44
> >> To: [EMAIL PROTECTED]
> >> Subject: Kernel Panic
> >>
> >>
> >> Hi
> >> Last saturday we had a kernel panic on our development system.
> >> Because of this, sapdb has crashed also and I am not able
> to start the
> >> database again.
> >> The database will come up with db_cold to the cold state,
> but db_warm
> >> gives the following error message:
> >>
> >> dbmcli on TST>db_warm
> >> ERR
> >> -24988,ERR_SQL: sql error
> >> -4008,Message not available
> >>
> >>
> >> The system runs sapdb-7.3.0.29 on redhat 7.3
>
> BM> You should save the log-pages of the crashed database in
> cold-mode.
>
> Thx Martin,
>
> This is what I have done so far:
> > util_connect dbm,xxxx
> > backup_start auto RECOVERY log
>
> As far as I understand, it has now saved the logpages to a file called
> autosave.xxx
>
> How can I restore these files and how do I get the database in the
> warm state again?
>
>
execute the following dbmcli-command at the original database
in offline mode:
backup_history_list -r LAST
you will get the backup-items. starting with a complete backup,
eventually an incremental backup and the log-backups needed.
1) create media-definitions for reading the data and log-backup with
backup_media_put ...
3) restore data
db_cold
util_connect
recover_start data_medium_name data
4) restore log starting with logBackupNo xxx until yyy
recover_start log_medium_name log xxx
recover_replace log_medium_name filename xxx+1
recover_replace log_medium_name filename xxx+2
recover_replace log_medium_name filename xxx+3
....
recover_replace log_medium_name filename yyy
recover_ignore
now the database should be in warm-mode.
Regards, Martin
P.S. please reply always to the list, because.....
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general