Poul Dige wrote:
<<
Regarding the need to replace a live database: We also have a
situation where a web application due to restrictions on access to
the live (writeable) database accesses a recent read-copy of the
database only. When this copy needs to be refreshed to the latest
verison of the writeable db we will have a problem if it is not
possible to force people off the read-database (given that this will
prevent restore of the most recent version).
So I am interested too in knowing IF it is legal or how it can be
legalized to restore/replace a running dabase, given that this has
been shut down first.

>>

If access to the database is through an alias, maybe you could
restore the backup to a new database and then (through some
"mechanism") change the aliases around. This way, the next time a
user connects he will access the new database. After a (short) while
every user will use the new one, and you can drop the old one.
Don't know if this is possible at all - maybe removing an alias (of
an active database) will cause problems. I've seen that changing the
alias during a restore (or maybe it was a backup?) wasn't totally
successful (it seems the process did a new connect (when finisheing?)
with the alias that no longer existed).


--
Aage J.