Holger Baer <holger.baer_at_science-computing.de> wrote in message news:<ciroqd$6ri$1_at_news.BelWue.DE>...
> I should have made clear that it was a tongue-in-cheek reply. But I
> was teaching a oracle for beginners course for a customer the other
> week, so I was probably a bit pedantic. Speaking of which: It's not
> exactly necessary to shutdown the database, as Hans kindly pointed
> out.
No, that's OK. It was my mistake, I should doublecheck it, before
posting. I thought: "that's simple, I have been doing it for years"
and just wrote it from memory not getting the fact that I didn't use
it recently. :-(
The point with an offlined tablespace was valid, but I never use it
this way. It could work only if data in a database are splitted among
tablespaces in the same way as among users. So at least part of
database users can work even with some tablespaces in an offline mode.
However, most of databases I have seen had as a tablespace layout
something like DATA01, DATA02, IDX01, IDX02 with data distributed
randomly, so no one can work with any of these tablespaces in an
offline mode. In this case, I think it is better to shutdown a
database instead of having users with weird errors in their
applications.
--
Dusan Bolek
http://www.db-support.com
Email: spambin_at_seznam.cz
Pls add "Not Guilty" to the subject, otherwise your email will face an
unpleasant end as SPAM.
Received on Thu Sep 23 2004 - 02:06:01 CDT
