RE: SAPDB Crash

Hello Pierre,

I think it is possible to "force" your db to online.

I feared that you would run into such problem because in 73 the undo log is 
written into the redo log too. This means(!) that without log these open 
transactions are not rollbacked after a "forced" restart (without undo log). 
But I need a terminal session to your database. If you are a sap customer it 
would be easy if you would open such connection via oss. If not I would offer 
you to directly connect to your database systems host via a ssh or telnet 
session.

Kind regards,
Uwe

>-----Original Message-----
>From: Pierre du Plessis [mailto:duplessis@xxxxxxxxxxx] 
>Sent: Thursday, December 30, 2004 2:41 AM
>To: Hahn, Uwe; maxdb@xxxxxxxxxxxxxxx
>Subject: AW: SAPDB Crash
>
>
>Hello Uwe
>
>I copied the dev spaces into a new Database that is exactly the same as
>the old one. (also the SYS dev space)
>
>I could backup the data cold but it says it requires a log for 
>recovery.
>( I have no log data.)
>
>Any way I can "force" the DB online after restoring ?
>
>Thanks
>
>Pierre.
>
>-----Ursprüngliche Nachricht-----
>Von: Hahn, Uwe [mailto:uwe.hahn@xxxxxxx] 
>Gesendet: Dienstag, 28. Dezember 2004 07:56
>An: Pierre du Plessis; maxdb@xxxxxxxxxxxxxxx
>Betreff: RE: SAPDB Crash
>
>Hello Pierre
>
>are you doing the backup with the dbmgui ? Could you send me the file
>dbm.prt ?
>Maybe it is only the command db_restartinfo which is requesting the log
>volume.
>(The procedure in the "p.s." I gave you is creating a "dummy" log
>volume.)
>
>kind regards,
>Uwe
>
>>-----Original Message-----
>>From: Pierre du Plessis [mailto:duplessis@xxxxxxxxxxx] 
>>Sent: Monday, December 27, 2004 4:51 PM
>>To: Hahn, Uwe; maxdb@xxxxxxxxxxxxxxx
>>Subject: AW: SAPDB Crash
>>
>>
>>Hello Uwe
>>
>>I set the database to ADMIN. Then I tried to start a backup but the db
>>is still asking for the Log Devspace. 
>>
>>Any other ideas (like a dummy log space) before I try to "attach" to a
>>new instance.
>>
>>Thanks
>>
>>Pierre.
>>
>>
>>
>>1637 WNG 11987 I/O      get_nodinfo: stat error for file
>>'/sapdb/VRT/saplog/DISKL001', No such file or directory
>>
>>
>>1637 ERR 11000 devopen  Unknown file MODE '/sapdb/VRT/saplog/DISKL001'
>>
>>
>>1637 ERR 11000 d0_vatta Cannot open devspace, Bad file descriptor
>>
>>
>>1637 ERR 11000 d0_vatta Devspace name '/sapdb/VRT/saplog/DISKL001'
>>
>>
>>1641 ERR 11000 vattach  dev0_vattach returned FALSE
>>
>>
>>1641     11000 vattach  '/sapdb/VRT/saplog/DISKL001' T5 failed
>>
>>
>>1641 ERR 53013 I/O      Could not open devspace
>>
>>
>>1641 ERR 53017 I/O      LOGDEV DEVNO: 1
>>
>>
>>1641 ERR 53016 I/O      /sapdb/VRT/saplog/DISKL001
>>
>>-----Ursprüngliche Nachricht-----
>>Von: Hahn, Uwe [mailto:uwe.hahn@xxxxxxx] 
>>Gesendet: Montag, 27. Dezember 2004 09:37
>>An: Pierre du Plessis; maxdb@xxxxxxxxxxxxxxx
>>Betreff: RE: SAPDB Crash
>>
>>If you have one of the newest builds of 73 a databackup in admin mode
>>without attaching the log area could go,
>>otherwise you will see attach and io errors in the file knldiag.
>>
>>After you have your backup you can install an instance with 
>>this backup.
>>
>>Kind regards
>>Uwe
>>
>>p.s. If you cannot do the backup in admin mode you could try to:
>>- copy away your data volumes
>>- reinitialize the database with current parameter set
>>- shutdown the new instance
>>- clear log
>>- copy back your old data volumes
>>- restart (if you get a db-ident mismatch error, email me again)
>>
>>
>>>-----Original Message-----
>>>From: Pierre du Plessis [mailto:duplessis@xxxxxxxxxxx] 
>>>Sent: Sunday, December 26, 2004 3:31 AM
>>>To: maxdb@xxxxxxxxxxxxxxx
>>>Subject: SAPDB Crash
>>>
>>>
>>>Hello 
>>> 
>>>Just a quick question:
>>> 
>>>I have a SAPDB 7.3 that crashed last week. I lost my log Dev 
>Space and
>>>all backups on the 2nd disk.
>>> 
>>>I still have the db software and all the data dev spaces.
>>> 
>>>Do I stand a chance to get my data back if I startup in ADMIN 
>>>mode, do a
>>>full backup and then restore the data into a new database ?
>>> 
>>>Yes, No or maybe ?
>>> 
>>>Thanks
>>> 
>>>Pierre.
>>>
>>
>>-- 
>>MaxDB Discussion Mailing List
>>For list archives: http://lists.mysql.com/maxdb
>>To unsubscribe:
>>http://lists.mysql.com/maxdb?unsub=duplessis@xxxxxxxxxxx
>>
>>
>
>-- 
>MaxDB Discussion Mailing List
>For list archives: http://lists.mysql.com/maxdb
>To unsubscribe:
>http://lists.mysql.com/maxdb?unsub=duplessis@xxxxxxxxxxx
>
>

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx