The db wizard is just using the dbmcli so it must be possible for you to migrate a 
database only
with the dbmcli. To look what you have to to manually you could look at dbm.prt.
There are all dbmcli commands logged.
kind regards
Uwe

> -----Original Message-----
> From: Groenewald, Duncan [mailto:[EMAIL PROTECTED]
> Sent: Dienstag, 9. September 2003 01:10
> To: Hahn, Uwe
> Cc: [EMAIL PROTECTED]
> Subject: RE: Migrating a 7.4.03.27 database to another server
> 
> 
> Well I am trying to migrate a database from one server to 
> another - both Wintel - so I have to create a new database on 
> the new server and recover from the backup.  I have finally 
> managed to get it to work using the Database Wizard to create 
> a database for recovery - and then using the DBM GUI to 
> restore from Media.  This seems to work OK now - although for 
> some reason though I am quite sure I could not get it to work 
> correctly when I first tried - hence the attempt to use the 
> DBMCLI.  Presumably one should be able to restore in the same 
> way using the DBMCLI commands.
> 
> Now I am trying to recovery the same database to a LINUX 
> server - but the database server failes with an environment 
> error - and I am using the WEBDBM interface to do this.  
> There seems to be some bugs with the WEBDBM gui - I can't for 
> example edit the volume settings.
> 
> Anyway I will keep at it and when I am consistently getting 
> it to work I will post the procedure here.
> 
> 
> Duncan
> 
> -----Original Message-----
> From: Hahn, Uwe [mailto:[EMAIL PROTECTED]
> Sent: Monday, 8 September 2003 4:47 PM
> To: Groenewald, Duncan
> Subject: RE: Migrating a 7.4.03.27 database to another server
> 
> 
> Hmm, this is looking strange.
> 
> The dbm.utl does not show your recover_start and does not 
> show the RETURNCODE -3014.
> Do you used the recover_start with the correct database ?
> 
> Uwe
> 
> 2003-09-05 16:52:35 3F5832B30001 0000   ICF INIT CONFIG
> => this is of course writte by util_execute init config
> 
> 2003-09-05 16:52:47 3F5832B30001 0001   RET RETURNCODE     0
> => this means the command was successfull
> 
> 2003-09-05 16:52:47              0000   RDB RESTORE DATA CANCEL
> => this means you have executed dbmcli ... recover_cancel
> => if you would have used recover_start a line like the 
> following must have been written.
> .................................0000   RDB RESTORE DATA 
> QUICK FROM '<your tape>' ...
> 
> 2003-09-05 16:52:47              0001   RET RETURNCODE -7078
> => this means that you cannot cancel what haven't been started.
> 
> 2003-09-05 16:52:48 3F5832C00003 0000   RST RESTART
> => because no data was loaded via restore data the restart is 
> failing (no RETURNCODE was printed)
> 
> 
> 
> > -----Original Message-----
> > From: Groenewald, Duncan [mailto:[EMAIL PROTECTED]
> > Sent: Montag, 8. September 2003 03:20
> > To: Hahn, Uwe
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: Migrating a 7.4.03.27 database to another server
> > 
> > 
> > 
> > 
> > -----Original Message-----
> > From: Hahn, Uwe [mailto:[EMAIL PROTECTED]
> > Sent: Friday, 5 September 2003 5:00 PM
> > To: Groenewald, Duncan
> > Subject: RE: Migrating a 7.4.03.27 database to another server
> > 
> > 
> > SQLM.en: ENG  -3014 Invalid end of SQL statement
> > 
> > Please send me the file dbm.utl there is the real command 
> > printed which is send to
> > the kernel.
> > 
> > > -----Original Message-----
> > > From: Groenewald, Duncan [mailto:[EMAIL PROTECTED]
> > > Sent: Freitag, 5. September 2003 08:55
> > > To: Hahn, Uwe; [EMAIL PROTECTED]
> > > Subject: RE: Migrating a 7.4.03.27 database to another server
> > > 
> > > 
> > > I just tried this but get the following error:
> > > 
> > > >util_execute INIT CONFIG
> > > OK
> > > 
> > > ---
> > > >recover_start IVTBKP DATA
> > > ERR
> > > -24988,ERR_SQL: sql error
> > > -3014,Message not available
> > > 
> > > 
> > > Any idea what this is ?
> > > 
> > > -----Original Message-----
> > > From: Hahn, Uwe [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, 5 September 2003 4:35 PM
> > > To: Groenewald, Duncan; [EMAIL PROTECTED]
> > > Subject: RE: Migrating a 7.4.03.27 database to another server
> > > 
> > > 
> > > read comments within the text:
> > > 
> > > > -----Original Message-----
> > > > From: Groenewald, Duncan [mailto:[EMAIL PROTECTED]
> > > > Sent: Freitag, 5. September 2003 04:53
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Migrating a 7.4.03.27 database to another server
> > > > 
> > > > 
> > > > I want to be able to backup a database and restore it on 
> > > > another server but seem unable to get this to work.  Having 
> > > > browsed various mailing lists it would appear the way to do 
> > > > this is by using the DBMCLI program to run the 
> following scripts:
> > > > 
> > > > # Create the database
> > > > dbmcli -n servername db_create IVT DMO,password
> > > > 
> > > > # Run the script to initialise the database
> > > > dbmcli -d IVT -u DMO,password -i inst01.cli
> > > > 
> > > > 
> > > > # INST01.CLI Script to create a new database
> > > > #
> > > > param_startsession
> > > > param_init
> > > > param_put MAXUSERTASKS 50
> > > > param_checkall
> > > > param_commitsession
> > > > param_addvolume 1 LOG LOG_001 F 2000
> > > > param_addvolume 1 DATA DAT_001 F 10000
> > > > db_admin
> > > > util_connect
> > > > util_execute INIT CONFIG
> > > > util_activate DBA,dagivs
> > > > util_release
> > > > load_systab -u DBA,dagivs -ud dagivs
> > > > # End of Script
> > > 
> > > This has created a data and log area for a new db instance.
> > > 
> > > > 
> > > > # Run the script to load the database
> > > > dbmcli -d IVT -u DMO,password -i inst02.cli
> > > > 
> > > > 
> > > > # INST02.CLI Script to reload the database from a backup
> > > > db_cold
> > > > util_connect DMO,dagivs
> > > > medium_put IVTBKP 'C:\Backups\IVTBKP' FILE DATA
> > > > recover_start IVTBKP DATA
> > > > util_release
> > > > 
> > > 
> > > This has overwritten the data area with the image of an old 
> > > db instance.
> > > 
> > > > # Set the database online
> > > > dbmcli -d IVT -u DMO,password db_online
> > > > 
> > > 
> > > Because every restart has to check the log if there is 
> > > something to be redone
> > > after the last savepoint, the log area is checked if it 
> > > belongs to the data area.
> > > 
> > > As you guess now the check must fail because.
> > > You tried to combine the data area from db instance A and the 
> > > log area from db instance B.
> > > 
> > > > 
> > > > The database fails to start - apparently because the log 
> > > > version is different to the database,  I saw some posting 
> > > > indicating it might be possible to delete the logs to fix 
> > > > this problem.
> > > > 
> > > > Any help would be appreciated.
> > > 
> > > You should try this:
> > > 
> > > # INST.CLI Script to create a new database from an old 
> > > instance (a db copy)
> > > #
> > > param_startsession
> > > param_init
> > > param_put MAXUSERTASKS 50
> > > param_checkall
> > > param_commitsession
> > > param_addvolume 1 LOG LOG_001 F 2000
> > > param_addvolume 1 DATA DAT_001 F 10000
> > > medium_put IVTBKP 'C:\Backups\IVTBKP' FILE DATA
> > > db_admin
> > > util_connect
> > > util_execute INIT CONFIG
> > > recover_start IVTBKP DATA
> > > db_online
> > > load_systab -u DBA,dagivs -ud dagivs
> > > # End of Script INST.CLI
> > > 
> > > kind regards
> > > Uwe
> > > 
> > > > 
> > > > Duncan Groenewald 
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > sapdb.general mailing list
> > > > [EMAIL PROTECTED]
> > > > http://listserv.sap.com/mailman/listinfo/sapdb.general
> > > > 
> > > 
> > 
> 
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to