Hi Tilo, I started now from scratch and tried to attach a new raw-device to a blank database. The problem seems to be the raw devices. On the currently running MAXDB 'raw -qa' outputs:
sapdb01:~ # raw -qa /dev/raw/raw1: bound to major 58, minor 5 /dev/raw/raw2: bound to major 58, minor 7 /dev/raw/raw3: bound to major 58, minor 6 sapdb01:~ # On the new system the 'raw -qa' output is empty! But why ? Regards, Dirk > -----Ursprüngliche Nachricht----- > Von: Heinrich, Tilo [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 14. Juni 2006 13:21 > An: maxdb@lists.mysql.com > Betreff: RE: fresh DB created, recovery doesn't work > > > Hello Dirk, > > Please have a look into knldiag or knldiag.err, to find out > more about the -71 (aka. "Session terminated by shutdown > (work rolled back)") during the db_activate. > > Best regards, > Tilo Heinrich > SAP Labs Berlin > > -----Original Message----- > From: Datzert, Dirk > Sent: Mittwoch, 14. Juni 2006 12:01 > To: maxdb@lists.mysql.com > Subject: fresh DB created, recovery doesn't work > > Hi all, > > I have a problem on restoring a full backup from an other > (identical) MAXDB system into a new hardware. > > System Data on both systems (SLES8): > > sapdb01:/var/opt/sdb/data/wrk/SAPDB01A # uname -a > Linux sapdb01 2.4.21-309-default #1 Tue May 16 23:32:53 UTC > 2006 i686 unknown > sapdb01:/var/opt/sdb/data/wrk/SAPDB01A # rpm -qa |grep maxdb > maxdb-ind-7.5.0.34-1 > maxdb-srv75-7.5.0.34-1 > maxdb-callif-7.5.0.34-1 > maxdb-web-7.5.0.34-1 > > Full backup file is available on the new hardware: > > sapdb01:/dasi/SAPDB01A # ll DATA > -rw-rw---- 1 sdb sdba 3546349568 Jun 13 01:13 DATA > > RAW-Device have correct permissions: > > sapdb01:/dasi/SAPDB01A # ll /dev/raw/raw[123] > crw-rw---- 1 sdb sdba 162, 1 Oct 21 2002 /dev/raw/raw1 > crw-rw---- 1 sdb sdba 162, 2 Oct 21 2002 /dev/raw/raw2 > crw-rw---- 1 sdb sdba 162, 3 Oct 21 2002 /dev/raw/raw3 > > RAW-Devices have correct block devices assigned: > > sapdb01:/dasi/SAPDB01A # more /etc/raw > # /etc/raw > raw1:system/data01 > raw2:system/log01 > raw3:system/data02 > > Block devices have matching sizes: > > sapdb01:/dasi/SAPDB01A # lvscan > lvscan -- ACTIVE "/dev/system/data01" [2 GB] > lvscan -- ACTIVE "/dev/system/data02" [2 GB] > lvscan -- ACTIVE "/dev/system/log01" [512 MB] > > With dem DBM-Gui I created a fresh database with identical > db-name as on the original server. > I restored the parameters from the backup medium, and the > backup medium was read succesfully. > The database seems to be created succesfully with the option > 'Create instance for recovery' and the > recovery wizard is started after the db is in admin mode. > > After I start the recover process I waited a long time (about > 1 hour), but not pages are transfered. > The DB is in offline state now. > > I found the follwing logging dbm.prt: > > sapdb01:/var/opt/sdb/data/wrk/SAPDB01A # more dbm.prt > -------------------------------------------------------------- > ---------------- > Date Time TID(hex) Typ MsgID Label Message > -------------------------------------------------------------- > ---------------- > 2006-06-14 10:37:06 0x000009c6 0 DBM > command backup_restart_info > > 2006-06-14 10:37:06 0x000009c6 ERR -24988 DBM > ERR_SQL: sql error > 0x000009c6 ERR -24988 DBM -902,I/O error > 2006-06-14 10:37:06 0x000009c6 0 DBM > command backup_history_open > > 2006-06-14 10:37:06 0x000009c6 ERR -24982 DBM > ERR_NOHISTORY: backup histo > ry file not found > 2006-06-14 10:37:17 0x000009c6 0 DBM > command db_activate > 2006-06-14 10:37:23 0x000009c6 ERR -24988 DBM > ERR_SQL: sql error > 0x000009c6 ERR -24988 DBM > -71,connection broken serve > r state 6 > > What is going wrong here ? I did a successfull recover 2 > times ago and have every step documented and repeated. > > Regards, > Dirk > > ------------------------------------- > > Der Inhalt dieser e-Mail ist ausschließlich für den > bezeichneten Adressaten > bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser e-Mail oder > dessen Vertreter sein sollten, so beachten Sie bitte, dass > jede Form der > Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des > Inhalts dieser e-Mail unzulässig ist. Wir bitten Sie, sich in > diesem Fall mit > dem Absender der e-Mail in Verbindung zu setzen. > > The information contained in this e-mail is intended solely > for the addressee. > Access to this e-mail by anyone else is unauthorized. If you > are not the > intended recipient, any form of disclosure, reproduction, > distribution, or any > action taken or refrained from in reliance on it, is > prohibited and may be > unlawful. Please notify the sender immediately. > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > ------------------------------------- Der Inhalt dieser e-Mail ist ausschließlich für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser e-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser e-Mail unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der e-Mail in Verbindung zu setzen. The information contained in this e-mail is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any form of disclosure, reproduction, distribution, or any action taken or refrained from in reliance on it, is prohibited and may be unlawful. Please notify the sender immediately. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
