Hello Miroslav, >(Sorry, not sure, if your first name is Heinrich or Tilo ;-).
No problem, it's Tilo. >I can even create small database on the G drive, >I just cannot create big database on the big (200GB) >G drive even though there is more than enough space. OK, that is an information to start with. Do you mind sending a dbm.prt and the complete knldiag from a failing database creation to this mailing list? >Then I can proceed with restore on the >small database but I get this error You have created the new (small) database and brought it into state ONLINE. Thereby you created some entries on the log volume, that do not match your data backup from the other database. If creating a database for restoring a data backup into it, do not start it into the ONLINE mode before restoring the backup. If you use DBMGUI's Installation Wizard, choose "Install for Recovery" instead of a plain installation of a database, when asked for. >Sorry I am bothering you with this so much That is what we are here for. Best regards, Tilo Heinrich SAP Labs Berlin -----Original Message----- From: Miroslav Halas [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2003 3:19 PM To: Heinrich, Tilo Cc: [EMAIL PROTECTED] Subject: RE: Crash during recovery Hi (Sorry, not sure, if your first name is Heinrich or Tilo ;-). Thanks for the advice. Yes, it works to create small database on C drive. I can even create small database on the G drive, I just cannot create big database on the big (200GB) G drive even though there is more than enough space. (Is it possibility that you check for the available disk space on a wrong drive ;-)? Then I can proceed with restore on the small database but I get this error -24895 shutdown of database occured [db_online -f]; -71, connection broken The err. file contains following message: -------------------------------------------------------------------------------- Date Time TID(hex) Typ MsgID Label Message-Text -------------------------------------------------------------------------------- 2003-11-14 08:02:00 --- Starting GMT 2003-11-14 08:02:00 7.4.3 Build 030-123-056-274 2003-11-14 08:05:57 --- Starting GMT 2003-11-14 08:05:57 7.4.3 Build 030-123-056-274 2003-11-14 08:06:37 0xF70 ERR 25 Log DBIdentifier of DataVolume (rack:TOOLCRIB_20031029_090227) and LogVolume (MATKO:TOOLCRIB_20031114_080429) does not 2003-11-14 08:06:37 0xF70 ERR 25 Log match 2003-11-14 08:06:37 0xF70 ERR 65 Log RestartArchiveLog: LogAndDataIncompatible 2003-11-14 08:06:37 0xF70 ERR 61 Log RESTART ERROR '3800' => SHUTDOWN IS FORCED The database will remain offline. I can get it to admin mode, but when I try to get it online, I get the same error and the error log looks like this -------------------------------------------------------------------------------- Date Time TID(hex) Typ MsgID Label Message-Text -------------------------------------------------------------------------------- 2003-11-14 08:02:00 --- Starting GMT 2003-11-14 08:02:00 7.4.3 Build 030-123-056-274 2003-11-14 08:05:57 --- Starting GMT 2003-11-14 08:05:57 7.4.3 Build 030-123-056-274 2003-11-14 08:06:37 0xF70 ERR 25 Log DBIdentifier of DataVolume (rack:TOOLCRIB_20031029_090227) and LogVolume (MATKO:TOOLCRIB_20031114_080429) does not 2003-11-14 08:06:37 0xF70 ERR 25 Log match 2003-11-14 08:06:37 0xF70 ERR 65 Log RestartArchiveLog: LogAndDataIncompatible 2003-11-14 08:06:37 0xF70 ERR 61 Log RESTART ERROR '3800' => SHUTDOWN IS FORCED 2003-11-14 08:16:09 --- Starting GMT 2003-11-14 08:16:09 7.4.3 Build 030-123-056-274 2003-11-14 08:16:14 0xBA8 ERR 25 Log DBIdentifier of DataVolume (rack:TOOLCRIB_20031029_090227) and LogVolume (MATKO:TOOLCRIB_20031114_080429) does not 2003-11-14 08:16:14 0xBA8 ERR 25 Log match 2003-11-14 08:16:14 0xBA8 ERR 65 Log RestartArchiveLog: LogAndDataIncompatible 2003-11-14 08:16:14 0xBA8 ERR 61 Log RESTART ERROR '3800' => SHUTDOWN IS FORCED Sorry I am bothering you with this so much, I had never expected it would be this difficult to just restore database on different computer so I am not sure how to deal with it. If you need me to, I can provde you with the backup data, it is not secret, it is about 6MB file. Miro ------------------------- Hello Miroslav, we have no idea what is happening. You are probably sure you configured your log volume to 6 GB. Have you the same problem when creating a very small database on C: or G: (e.g. 25MB Data, 15MB Log)? Best regards, Tilo Heinrich SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
