Hi Steffen, All,
Thanks for the note. I have the DBEXTRACT and DBLOAD working now...but it
still only cuts the import time down to 18 minutes!!
Have been wondering some more whether I can just do a backup of the data,
and then restore it?
What are the implications of this? We do not care about the log at this
stage, as it is set to "auto overwrite on", and at this stage we will be
reinstalling the app and just reloading all the exported (backed-up) data.
I have tried this, and ran into an error I couldn't find details of
anywhere:
I backed up the database with:
>dbmcli -d <db> -u <user>,<pswd> medium_put portalBack1
c:\portalBack1 FILE DATA 0 0 YES
>dbmcli -d <db> -u <user>,<pswd> -uUTL -c backup_start portalBack1
That all seems fine. I then stop and drop the database, recreate it and
then try and restore it using:
>dbmcli -uUTL -d <db> -u <user>,<pswd>
recover_start portalBack1 DATA
I then get the error:
-24986...media file not found
I **have** been able to use the DBM GUI to chose the backup medium and
restore it - except then it won't change from being OFFLINE.
Please could you let me know why the dbmcli can't find the media file? I
think I remember reading about an error after restoring and the db not
going warm due to the log backup not being restored? I don't want to do
anything with the log - is that possible? If not, what do I have to do?
many thanks,
David
"Schildberg, Steffen" <[EMAIL PROTECTED]>@listserv.sap.com on
18/08/2003 07:26:01 AM
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: RE: Quickest way to export and import data
Hi David,
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
> Subject: RE: Quickest way to export and import data
>
> At this point we just want the quickest way to do it, and
> don't mind it being unreadable.
>
> So, I switched to the DBExtract and DBLoad - this works fine,
> until I try
> and use the database and I discovered that it is now readonly
> until I do a
> backup! Doesn't this defeat the purpose?! I believe this is
> true for the fastload, too.
>
No, it doesnt defeat the purpose at all. What if the newly imported db
crashes and the exported does not longer exist. Yes it's a kind
of artificial case but who knows.
BUT there exist a way out: if you don't mind loosing your data
you could do a DBLOAD and then running a 'SET NOLOG OFF' command
in a utility session.
Using dbmcli that would be:
dbmcli -u <dbm user name>,<pw> -d <db name>
util_connect
util_execute set nolog off
util_release
That switches the 'read only' flag for all tables off. The same
applies for FASTLOAD, too. But again
in case of a crash you can't restore that db to it's initial state
if not doing a backup.
Regards,
Steffen
--
Steffen Schildberg
SAP DB Team
SAP Labs Berlin
_______________________________________________
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
