Hi Stephen,

I found the following:

In dbm.utl only these two lines:
(This file is written by the database core and contains dbm commands used by the dbm 
server.)

2003-12-22 08:55:24 3FE721FC0001 0000   IC1 CREATE INSTANCE SYSDBA DBA
2003-12-22 09:04:45 3FE721FC0001 0001   RET RETURNCODE     0

This means, that the database volumes are initialized and there was no contents 
restored.

The correct example would look like this and it shows the extended initialization 
coupled with data recovery.

2003-12-23 10:32:39 3FE80BB70001 0000   IC1 CREATE INSTANCE WITH RESTORE DATA FROM 
'xinitdb.sav' FILE  BLOCKSIZE 8 MEDIANAME 'XINITDB'
2003-12-23 10:32:42 3FE80BB70001 0001   RET RETURNCODE     0
2003-12-23 10:32:42 3FE80BB70001 0002   TAP DATE.............. 2003-12-23
2003-12-23 10:32:42 3FE80BB70001 0003   TAP TIME.............. 10:32:41
2003-12-23 10:32:42 3FE80BB70001 0004   TAP SERVERDB.......... SUT75
2003-12-23 10:32:42 3FE80BB70001 0005   TAP SERVERNODE........ <node>
2003-12-23 10:32:42 3FE80BB70001 0006   TAP KERNEL VERSION.... Kernel    7.5.0    
Build 009-003-059-738
2003-12-23 10:32:42 3FE80BB70001 0007   TAP PAGES TRANSFERRED.         240
2003-12-23 10:32:42 3FE80BB70001 0008   TAP PAGES LEFT........           0
2003-12-23 10:32:42 3FE80BB70001 0009   TAP NO OF VOLUMES.....           1
2003-12-23 10:32:42 3FE80BB70001 000A   TAP MEDIA NAME........ XINITDB
2003-12-23 10:32:42 3FE80BB70001 000B   TAP TAPE NAME......... xinitdb.sav
2003-12-23 10:32:42 3FE80BB70001 000C   TAP TAPE ERRORTEXT.... UNDEF
2003-12-23 10:32:42 3FE80BB70001 000D   TAP TAPE LABEL........ DAT_00001
2003-12-23 10:32:42 3FE80BB70001 000E   TAP IS CONSISTENT..... TRUE
2003-12-23 10:32:42 3FE80BB70001 000F   TAP FIRST IO SEQUENCE.        1041
2003-12-23 10:32:42 3FE80BB70001 0010   TAP LAST IO SEQUENCE.. UNDEF
2003-12-23 10:32:42 3FE80BB70001 0011   TAP DBSTAMP1 DATE..... 2003-12-17
2003-12-23 10:32:42 3FE80BB70001 0012   TAP DBSTAMP1 TIME..... 09:17:49
2003-12-23 10:32:42 3FE80BB70001 0013   TAP DBSTAMP2 DATE..... UNDEF
2003-12-23 10:32:42 3FE80BB70001 0014   TAP DBSTAMP2 TIME..... UNDEF
2003-12-23 10:32:42 3FE80BB70001 0015   TAP BD PAGE COUNT.....         223
2003-12-23 10:32:42 3FE80BB70001 0016   TAP TAPEDEVICES USED..           1
2003-12-23 10:32:42 3FE80BB70001 0017   TAP DB_IDENT.......... <identifier>
2003-12-23 10:32:42 3FE80BB70001 0018   TAP MAX USED DATA PNO.           0
2003-12-23 10:32:48 3FE80BC00004 0000   RST RESTART
2003-12-23 10:32:50 3FE80BC00004 0001   RET RETURNCODE     0

The file dbm.prt which is written by the dbm server shows me these lines:

2003-12-22 08:54:53 0x0000024c              0 DBM      command db_admin 
2003-12-22 08:55:24 0x00000bf4              0 DBM      command medium_put completeFile 
c:\sapdb-esnipe14-bk010.data FILE DATA 0 8 YES 
2003-12-22 08:55:24 0x00000bf4              0 DBM      command db_activate 
2003-12-22 09:04:45 0x00000bf4              0 DBM      command db_online

The interesting command is db_activate which executes CREATE INSTANCE ... but the 
complete command is not shown so I don't know if db_activate was called with the 
option "recover".

The conclusion is that your script shows "db_activate recover..." but the recover 
options is not considered. Your output file does not show the executed commands either 
only return values are printed (OK).
Please verify that the correct commands are used.

So you cannot find your data until it is really recovered.

Kind regards
Uwe

-----Urspr�ngliche Nachricht-----
Von: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 22. Dezember 2003 18:39
An: Hahn, Uwe; [EMAIL PROTECTED]
Betreff: RE: MaxDB 7.5.0.5 Restore problems - no data after restore

I responded to Uwe in a private thread with copies of my entire wrk
directory.  However, I want to correct the outdated subject on this public
post.  At first I had a problem with logs due to syntax changes in 7.5.  Got
past that.  The current issue now is more with the restore not working (no
data), despite no syntax errors.

To review.  We are backing up with these commands on Windows 2000 Service
Pack 4:

dbmcli -n localhost -d MYDB1 -u DBM,** medium_put completeF
c:\MaxDB-servermy1-bk000.data FILE DATA 0 8 YES
dbmcli -n localhost -d MYDB1 -u DBM,** -uUTL -c backup_start completeF
MIGRATION

Then restoring with this script on a Windows XP Service Pack 1 system:

  http://www.IPCoast.com/MaxDB-Restore02.txt

The script runs without error - but after completion the 'info state' shows
only 2MB of data when the restore file and source database is 9GB.  The data
is also not there when tests are performed with client SELECT.

The backup source is a SAPDB server that started life as 7.4 and was
upgraded to MaxDB 7.5 and is working perfectly fine otherwise.  Of course,
we currently have no way to recover this MaxDB 7.5 database if it corrupts
or crashes - so we are anxious to get attention on this matter.  Good news
is that we run parallel hosting sites and only upgraded one site to MaxDB
7.5.  We are still replicating INSERT/UPDATE statements with our second site
running SAPDB 7.4 and backup/restore works fine on SAPDB 7.4 server.

  Stephen Gutknecht
  Full time traveler, currently in Lake Havasu City, Arizona USA
  Spending New Years in Las Vegas with my wife, always wanting to meet
people!


-----Original Message-----
From: Hahn, Uwe [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 22, 2003 1:27 AM
To: 'Stephen Gutknecht (SAPDB)'; [EMAIL PROTECTED]
Subject: AW: MaxDB 7.5.0.5 Restore problems - log file not created


Hello Stephen,

could you please send me the dbm.utl and dbm.knl and dbm.prt from your
restored instance, because the output.txt and knldiag
does not give any usefull hint in this case.
I need the information what was really restored to your database.

Uwe

-----Urspr�ngliche Nachricht-----
Von: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED] 
Gesendet: Samstag, 6. Dezember 2003 22:46
An: Hahn, Uwe; [EMAIL PROTECTED]
Betreff: RE: MaxDB 7.5.0.5 Restore problems - log file not created

Uwe (and anyone else who can help),

I foolishly assumed that because I got OK on all steps and ONLINE status..
that the data was there.  However, this weekend I sat down to do some work
with the data and it is missing!  None of my tables are actually restored,
and 'info state' shows only 2MB of consumed pages where the backup  source
datbase and backup file is 9GB!

This is from MaxDB 7.5.0.5 to 7.5.0.5 on Windows 2000 to Windows XP
Professional. Can you review my restoration steps again and see if there is
some error?

dbmcli -n localhost -d MYDB1 -u DBM,** medium_put completeF
c:\MaxDB-servermy1-bk000.data FILE DATA 0 8 YES
dbmcli -n localhost -d MYDB1 -u DBM,** -uUTL -c backup_start completeF
MIGRATION

Script I am using for restore:

  http://www.ipcoast.com/MaxDB-Restore02.txt

I am ONLY using the data file, I am not concerned with the LOG files.  I
just need a snapshot.

Thankfully we left one of our systems at 7.4.3.027 and are replicating our
INSERT/UPDATE statements.  I am not having problems with 7.4.3.027 to
7.4.3.027 backup and restore.

  Stephen Gutknecht



-----Original Message-----
From: Hahn, Uwe [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 04, 2003 12:44 AM
To: 'Stephen Gutknecht (SAPDB)'; [EMAIL PROTECTED]
Subject: AW: MaxDB 7.5.0.5 Restore problems - log file not created


I have included a few changes.
Uwe
[...]
rem ##########################################################
rem ### startup database
rem ##########################################################

dbmcli -d %SID% -u %uDBM%,%uDBMPW% db_admin

echo .
echo ***
echo *** Just completed db_admin
echo ***
:Skip1
echo ***
echo *** Next step is to start restore!
echo ***
pause

echo medium_put completeFile %restoreFile% FILE DATA 0 8 YES >> param.tmp
echo util_connect > param.tmp
echo db_activate recover completeFile >> param.tmp
echo db_online >> param.tmp

type param.tmp | dbmcli -d %SID% -u %uDBM%,%uDBMPW%

echo *** 
echo *** Did the database go warm?  Next step is to load system tables.
echo *** 
pause

rem look at the state - is it ONLINE ?
dbmcli -d %SID% -u %uDBM%,%uDBMPW% db_state

rem load database system tables
dbmcli -d %SID% -u %uDBM%,%uDBMPW% load_systab -u %uDBA%,%uDBAPW% -ud domain
[...]

-----Urspr�ngliche Nachricht-----
Von: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 4. Dezember 2003 09:01
An: Hahn, Uwe; [EMAIL PROTECTED]
Betreff: RE: MaxDB 7.5.0.5 Restore problems - log file not created

Hello Uwe,

I tried doing it in several places, not making progress.  Getting various
errors.  Including the following when I put it after db_start:

dbmcli on TEST4>ERR
-24988,ERR_SQL: sql error
-101,Message not available

Can you pretty please review my script and tell me where to insert
db_activate with RECOVER option?

http://www.IPCoast.com/MaxDB-Restore01.txt

Any other things you notice missing / incorrect in my script?  I seem to
have the worst luck with syntax changes to the restore process.

Thank you.

  Stephen Gutknecht

-- 
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]

Reply via email to