MaxDB Recovery / Attach error

[stefan_koehler]

Hello guys,

i really need your assistance with a MaxDB problem. At first i have to say that i am not the MaxDB professional and just look at it once a year

Now my problem:

We need to restore our MaxDB database on another windows server, because some data was deleted. The original is running on a Windows 2003 SP1 with MaxDB 7.5.00.39. The restore system ins running on a Windows 2003 SP2 with MaxDB 7.5.00.50, because i didn't find the old original version on SMP.

I defined a new database with the GUI on the new server with the exact same data and logfiles. Then i configured the backup tool (ADINT) and i can see the backups. If i now try to create / restore the database it aborts and in the knldiag.err i can see the following.

-
Date       Time       TID(hex) Typ MsgID Label    Message-Text
-
2008-12-15 17:40:06                               --- Starting GMT 2008-12-15 16:40:06           7.5.0    Build 050-123-186-888
2008-12-15 17:40:09      0xDE8 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:40:09      0x9AC ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:40:10      0xDE8 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:40:10      0x9AC ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:40:11      0xDE8 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:40:11      0x9AC ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:45:53      0xDE8 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:45:53      0x9AC ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:45:55                               ___ Stopping GMT 2008-12-15 16:45:55           7.5.0    Build 050-123-186-888
2008-12-15 17:47:20                               --- Starting GMT 2008-12-15 16:47:20           7.5.0    Build 050-123-186-888
2008-12-15 17:47:23      0xE00 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:47:23      0x388 ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:47:48      0xE00 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:47:48      0x388 ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:47:49      0xE00 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:47:49      0x388 ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:48:26      0xE00 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:48:26      0x388 ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:48:46      0xE00 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:48:46      0x388 ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 17:48:47      0xE00 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2
2008-12-15 17:48:47      0x388 ERR 20014 IOMan    Attach error on data volume 1: could not open volume
2008-12-15 18:55:36      0x310 ERR 52012 RESTORE  error occured, basis_err 3700
2008-12-15 21:41:43      0x388 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:41:45      0x388 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:41:47      0x388 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:41:49      0x388 ERR 20024 IOMan    Bad restart page on Data volume 1 blockno 1
2008-12-15 21:41:49      0x388 ERR 18196 DBCRASH  vabort:Emergency Shutdown, IOMan_Manager.cpp: 760
2008-12-15 21:42:35                               --- Starting GMT 2008-12-15 20:42:35           7.5.0    Build 050-123-186-888
2008-12-15 21:42:39      0x2E0 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:42:41      0x2E0 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:42:43      0x2E0 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:42:45      0x2E0 ERR 20024 IOMan    Bad restart page on Data volume 1 blockno 1
2008-12-15 21:42:45      0x2E0 ERR 18196 DBCRASH  vabort:Emergency Shutdown, IOMan_Manager.cpp: 760
2008-12-15 21:53:29                               --- Starting GMT 2008-12-15 20:53:29           7.5.0    Build 050-123-186-888
2008-12-15 21:53:34      0xB50 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:53:36      0xB50 ERR 20013 IOMan    Bad page on data volume 1 blockno 1
2008-12-15 21:53:38      0xB50 ERR 20013 IOMan    Bad page on data volume 1 blockno 1

I have enough space on disk - the disk layout is the same as on the productive site. The volume "D:\sapdb\SDB\sapdata\DISKD0001" itself exists. I have no idea what's the problem with it.

Can you help me?

Regards

Stefan

[lbreddemann]

>

> Hello guys,
> i really need your assistance with a MaxDB problem. At first i have to say that i am not the MaxDB professional and just look at it once a year 
Hi Stefan,
let's see what we can do here ...
> We need to restore our MaxDB database on another windows server, because some data was deleted. The original is running on a Windows 2003 SP1 with MaxDB 7.5.00.39. The restore system ins running on a Windows 2003 SP2 with MaxDB 7.5.00.50, because i didn't find the old original version on SMP.
That's not an issue at all. All MaxDB data backups are designed to be recoverable into a newer build of the same release.
> I defined a new database with the GUI on the new server with the exact same data and logfiles.
Since MaxDB does not rely on the physical storage layout this was not necessary.
>Then i configured the backup tool (ADINT) and i can see the backups. If i now try to create / restore the database it aborts and in the knldiag.err i can see the following.
> 

> -

---

> Date Time TID(hex) Typ MsgID Label Message-Text

> -

---

> 2008-12-15 17:40:06 --- Starting GMT 2008-12-15 16:40:06 7.5.0 Build 050-123-186-888

> 2008-12-15 17:40:09 0xDE8 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2

On Windows returncode 2 means 'file not found'. (You can easily check this via 'xsysrc 2' or 'net helpmsg 2').

Since MaxDB will create the files during the create instance for recovery procedure, this is quite odd.

Could you post the dbm.prt log file please?

> 2008-12-15 17:48:47 0xE00 ERR 18159 VOLUMEIO Could not open volume 'D:\sapdb\SDB\sapdata\DISKD0001', rc = 2

> 2008-12-15 17:48:47 0x388 ERR 20014 IOMan Attach error on data volume 1: could not open volume

> 2008-12-15 18:55:36 0x310 ERR 52012 RESTORE error occured, basis_err 3700

> 2008-12-15 21:41:43 0x388 ERR 20013 IOMan Bad page on data volume 1 blockno 1

> 2008-12-15 21:41:49 0x388 ERR 20024 IOMan Bad restart page on Data volume 1 blockno 1

> 2008-12-15 21:41:49 0x388 ERR 18196 DBCRASH vabort:Emergency Shutdown, IOMan_Manager.cpp: 760

>

This is even more irritating and looks like that the data volume file 'D:\sapdb\SDB\sapdata\DISKD0001' was somehow created at the right location but not by the MaxDB kernel.

Basically this error reads 'ok, I found a file there and I had a look into it, but I've no idea what this file is for!'

> I have enough space on disk - the disk layout is the same as on the productive site. The volume "D:\sapdb\SDB\sapdata\DISKD0001" itself exists. I have no idea what's the problem with it.

As I wrote, this looks like something did go wrong during the creation of the instance.

The disk layout does not matter and the volume file does not seem to be a valid MaxDB volume.

Did you follow note '129352 - Homogeneous system copy with MaxDB (SAP DB)' to recover the database?

The dbm.prt log really should tell us more here.

regards,

Lars

[stefan_koehler]

Hello Lars,

thanks for your prompt response.

Here is the requested output from dbm.prt.

-
Date       Time     TID(hex)   Typ MsgID      Label    Message
-
2008-12-15 17:40:11 0x00000790              0 DBM      command backup_restart_info 
2008-12-15 17:40:11 0x00000790 ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000790 ERR     -24988 DBM      -902,I/O error
2008-12-15 17:40:24 0x00000790              0 DBM      command backup_media_getall 
2008-12-15 17:40:24 0x00000790 ERR     -24986 DBM      ERR_NOMEDIA: media file not found
2008-12-15 17:40:35 0x00000790              0 DBM      command backup_media_put "ADSM_DATA" "
.\pipe\DATA" PIPE DATA 0 0 NO NO ""     
2008-12-15 17:40:47 0x00000790              0 DBM      command backup_media_put "ADSM_INC" "
.\pipe\INC" PIPE PAGES 0 0 NO NO ""      
2008-12-15 17:40:57 0x00000790              0 DBM      command backup_media_put "ADSM_LOG" "
.\pipe\LOG" PIPE LOG 0 0 NO NO ""
2008-12-15 17:42:17 0x00000cac              0 DBM      command backup_ext_ids_get ASDM_DATA SDB COBS1019
2008-12-15 17:42:26 0x00000cac              0 DBM      command backup_ext_ids_list 
2008-12-15 17:45:53 0x00000790              0 DBM      command backup_restart_info 
2008-12-15 17:45:53 0x00000790 ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000790 ERR     -24988 DBM      -902,I/O error
2008-12-15 17:45:53 0x00000790              0 DBM      command db_offline 
2008-12-15 17:47:20 0x00000a00              0 DBM      command db_admin -f     
2008-12-15 17:47:23 0x00000a00              0 DBM      command backup_restart_info 
2008-12-15 17:47:23 0x00000a00 ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000a00 ERR     -24988 DBM      -902,I/O error
2008-12-15 17:47:48 0x00000c5c              0 DBM      command backup_restart_info 
2008-12-15 17:47:48 0x00000c5c ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000c5c ERR     -24988 DBM      -902,I/O error
2008-12-15 17:47:49 0x00000c5c              0 DBM      command backup_restart_info 
2008-12-15 17:47:49 0x00000c5c ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000c5c ERR     -24988 DBM      -902,I/O error
2008-12-15 17:48:26 0x00000e14              0 DBM      command backup_restart_info 
2008-12-15 17:48:26 0x00000e14 ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000e14 ERR     -24988 DBM      -902,I/O error
2008-12-15 17:48:46 0x00000f3c              0 DBM      command backup_restart_info 
2008-12-15 17:48:46 0x00000f3c ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000f3c ERR     -24988 DBM      -902,I/O error
2008-12-15 17:48:47 0x00000f3c              0 DBM      command backup_restart_info 
2008-12-15 17:48:47 0x00000f3c ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000f3c ERR     -24988 DBM      -902,I/O error
2008-12-15 17:50:06 0x00000f3c              0 DBM      command backup_restore "ADSM_DATA" DATA EBID "<BACKUP_ID>"    
2008-12-15 17:57:32 0x00000f3c ERR     -24920 DBM      ERR_BACKUPOP: backup operation was unsuccessful
                    0x00000f3c ERR     -24920 DBM      The backup tool failed with -1 as sum of exit codes. A cancel of the database request failed.
2008-12-15 21:39:32 0x00000f3c              0 DBM      command backup_restore "ADSM_DATA" DATA EBID "<BACKUP_ID>"    
2008-12-15 21:39:32 0x00000f3c ERR     -24924 DBM      ERR_DBREQ: cannot start database kernel request
                    0x00000f3c ERR     -24924 DBM      The database was unable to fulfill a request (-8888, unbalanced request/reply).
2008-12-15 21:39:39 0x00000f3c              0 DBM      command backup_restore_cancel 
2008-12-15 21:39:39 0x00000f3c ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000f3c ERR     -24988 DBM      -8888,unbalanced request/reply               
2008-12-15 21:40:36 0x00000e68              0 DBM      command util_connect 
2008-12-15 21:40:36 0x00000e68 ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000e68 ERR     -24988 DBM      1,utility session is already in use       
2008-12-15 21:41:33 0x000009e4              0 DBM      command util_connect 
2008-12-15 21:41:33 0x000009e4 ERR     -24988 DBM      ERR_SQL: sql error
                    0x000009e4 ERR     -24988 DBM      1,utility session is already in use       
2008-12-15 21:42:34 0x00000948              0 DBM      command db_admin -f     
2008-12-15 21:45:43 0x000009e4              0 DBM      command backup_restart_info 
2008-12-15 21:45:43 0x000009e4 ERR     -24994 DBM      ERR_RTE: runtime environment error
                    0x000009e4 ERR     -24994 DBM      1,connection broken [203]
2008-12-15 21:46:39 0x00000948              0 DBM      command backup_restart_info 
2008-12-15 21:46:39 0x00000948 ERR     -24994 DBM      ERR_RTE: runtime environment error
                    0x00000948 ERR     -24994 DBM      1,connection broken [203]
2008-12-15 21:53:29 0x00000a28              0 DBM      command db_admin -f     
2008-12-15 21:57:34 0x00000a28              0 DBM      command backup_restart_info 
2008-12-15 21:57:34 0x00000a28 ERR     -24994 DBM      ERR_RTE: runtime environment error
                    0x00000a28 ERR     -24994 DBM      1,connection broken [203]
2008-12-15 22:04:39 0x00000a28              0 DBM      command util_connect 
2008-12-15 22:04:39 0x00000a28 ERR     -24988 DBM      ERR_SQL: sql error
                    0x00000a28 ERR     -24988 DBM      1,database not running                    

I have read the suggested sapnote #129352 and i did only one thing another way.

I created an SDB instance by click on CREATE and selected "Instance for Recovery".

I didn't follow the way "-> Database Manager GUI -> Restoring Data -> Restoring After Initializing a Database Instance".

Regards

Stefan

[lbreddemann]

> I have read the suggested sapnote #129352 and i did only one thing another way.

> I created an SDB instance by click on CREATE and selected "Instance for Recovery".

> I didn't follow the way "-> Database Manager GUI -> Restoring Data -> Restoring After Initializing a Database Instance".

Hmm... the dbm.prt does not tell the same story here...

For the sequence you described there should have been a "db_activate" command in the DBM.PRT file.

As the "db_activate" is the command that actually performs the creation of the data/log volume files this explains, why there weren't no such files at first.

Are you using the current version of the DBMGUI (7.6.03)? If not, make sure to download the current version before.

Also drop the current instance and begin from scratch here.

An alternative approach could also be to just create an empty instance with the right size of the data area (you can layout the files as you like) and afterwards perfom a "recovery with initialization" to this instance. That way the files are surely there...

Good luck and nice to see you on the MaxDB as well!

regards,

Lars

[stefan_koehler]

Hello

> Are you using the current version of the DBMGUI (7.6.03)?

No i am using 7.5.00.18

I will try it again with the "Initializing" - if it also not working i will open a SAP call for that tomorrow.

UPDATE: Thanks Lars for the tip with the sapnote. I tried it with the "Initializing" and it works now.

Regards

Stefan