RE: Saving a group of tables on a database refresh
- From: Rachel Carmichael <wisernet100@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Tue, 17 Aug 2004 12:47:46 -0700 (PDT)
Carel-Jan,
shows what happens when I skim threads instead of reading EVERY line of
every mesage.
yep, in that case, then making the tablespace read-only should work.
As for having multiple tablespaces under a single schema, um, isn't
that the methodology of "small","medium" and "large" tablespaces?
(otherwise known as the Goldilocks method of table distribution).
I won't even bother to re-start the "tables and indexes in separate
tablespaces" debate. :)
Rachel
--- Carel-Jan Engel <cjpengel.dbalert@xxxxxxxxx> wrote:
> 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@xxxxxxxx wrote:
> >
> > >
> > > Just a thought:
> > > Put the tables in their own tablespace and make it read only.
> > > Import.
> > > Then make it read write.
> > >
> > >
> >
>
>
>
>
>
>
> ----------------------------------------------------------------
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> ----------------------------------------------------------------
> To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
> put 'unsubscribe' in the subject line.
> --
> Archives are at //www.freelists.org/archives/oracle-l/
> FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
> -----------------------------------------------------------------
>
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
