I can pass on a tip that another team member ([EMAIL PROTECTED]) discovered
on our test database.
We avoid the read only condition without a second backup as follows:
Create an incremental backup after the original full backup (migration
option) which takes just a few seconds. (The database was inactive at
the time).
Then apply this incremental to the migrated database after the full
"restore". The database is no longer read only.
We do this on a test database that we need to restore to its original
state over and over. I can't make any claims on a production system.
Here are examples from our usage:
- add incremental backup medium
medium_put incr /tmp/incremental FILE PAGES 0 8 YES
-Do an incremental backup right after the complete backup:
backup_start migrate migration
backup_start incr migration
-Import incremental backup after importing the complete backup
recover_start migrate
recover_start incr
We were thinking of adding this to the wiki page on migration, but would
like some confirmation first that others find it as effective as we do.
Let us know if it works for you.
I cannot understand why a backup made after a checkpoint ("migration"
option) should require a backup step, but at least this approach speeds
up the process. Perhaps someone can explain why this procedure works?
If our database crashes, will we be unable to recover without a complete
restore, as suggested in Peter's previous email? In our case we don't
care, but if we put something on a wiki page, we want to be clear about
its effects.
Thanks for letting us know you experienced this problem too.
On Fri, 2002-12-06 at 03:27, Warga (ext_Zip) Marco wrote:
> Thats why I said its a waste of time for test installations and should be
> optional and enabled by default :)
> If I don't care if my test database works after a crash or not I don't need
> a backup.
> Just imagine you play around with loading/unloading large databases with
> repm and just want to know if it works and your client software works and
> not actually doing it in a productive scenario.
> Beeing forced to do a backup in these scenarios after each and every load is
> annoying and takes alot of time for nothing.
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Freitag, 6. Dezember 2002 12:09
> > To: Warga (ext_Zip) Marco; '[EMAIL PROTECTED]'
> > Subject: Re: Table is read only!
> >
> >
> > Hello,
> > On Freitag, 6. Dezember 2002 09:36, Warga (ext_Zip) Marco wrote:
> > > I also ran into this error before.
> > > Why is it that one is *forced* to do a backup after a load?
> > > I mean if I load a database for test reasons a full backup
> > may just be
> > > a waste of time.
> > >
> > > I would suggest do make this "feature" optional and enabled by
> > > default, not mandatory. Or is there a technical reason?
> > >
> > loading is so fast because it does no logging.
> > So you have to do a backup afterwards or you will never be
> > able to proceed
> > with anything like recovery if you DB crashes.
> >
> > Peter Willadt
> >
> _______________________________________________
> 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
