| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Saving a group of tables on a database refresh
Rachel,
I think that the idea is that the tables that should not be overwritten
are stored in the separate tablespace. This tablespace is made R/O then,
just to prevent overwriting them by the import. The tables that should
be refreshed, will be in a R/W tablespace, can be truncated or dropped,
and filled again by the import.
As Cary says, the best tuning is not to execute the SQL at all. I would preferably not export the unwanted data (saves time, disk space and whatever more), but if the data is in the .dmp file already, I would go for the tables= clause as suggested before in this thread. No fear for unforeseen extra rows in the tables because they didn't exist, just a slightly more complicated import script. Just specify the tables you want to import. Straight forward, understandable by any successor of yours (what the heck are they doing here? why two tablespaces for one schema? Why is it made read-only?) Less job-security of course.
Best regards,
Carel-Jan Engel
===
If you think education is expensive, try ignorance. (Derek Bok)
===
On Tue, 2004-08-17 at 21:04, Rachel Carmichael wrote:
> Um, I'm sure I'm misunderstanding something.
>
> But if a tablespace is read only, how does one import into it? Isn't
> the definition of read only that one can NOT write to it?
>
>
> --- Stephen.Lee_at_DTAG.Com wrote:
>
> >
> > Just a thought:
> > Put the tables in their own tablespace and make it read only.
> > Import.
> > Then make it read write.
> >
> >
>
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Tue Aug 17 2004 - 14:12:15 CDT
 |
 |