Re: RE: Renaming tablespace by updating SYS.TS$

We are renaming them in our staging database.

Let me explain further. We have:

1. Staging Database.. where we load the data to a staging table, then we scrub it and move it to another tablespace in its 'final' verseion before transport
2. Production server on a remote site.

We change the name in our staging server. The users dont have access to it. Its just for loading and scrubbing. If we transport tablespace 'A' every day then we have 50 tablespace A's. So we need new names. Now lets say we do use 2 tablespaces in our staging server? Then we need to copies of our tables in their final veresion. These are upwards of 40-50 GBs. These would need to be copied EVERY day. This is alot of additional I/O on top of:

1. Loading data
2. Inserts, updates, and deletes to scrub the data
3. Bandwidth to transport the tablespace to the remote site.
4. Once at the remote site we actually import them to multiple databases for different applications.

This has to be done serially and takes time. We cant take on the additional I/O of maintaining 2 identical tablespaces in our staging server.

Was it clear this time?
----- Original Message -----
To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com> Sent: Friday, May 09, 2003 7:26 PM

> If you have 2 schema's, and you use synonyms to point the app
> to the current schema, *why* are you renaming the tablespace?
>
> All you have to do is stop doing that. Just use 2 tablespace names
> and alternate between them. Renaming them is not buying you
> anything.
>
> Jared
>
>
>
>
>
>
> <rgaffuri_at_cox.net>
> Sent by: root_at_fatcity.com
> 05/09/2003 02:12 PM
> Please respond to ORACLE-L
>
>
> To: Multiple recipients of list ORACLE-L
<ORACLE-L_at_fatcity.com>
> cc:
> Subject: RE: RE: Renaming tablespace by updating SYS.TS$
>
>
> my fault on the explanation. We also have 2 schemas. One is currently
> active with a default tablespace of CURRENT_TABLESPACE.
>
> We have an inactive Schema, whose default tablespace becomse
> NEWTABLESPACE. We then change the synonyms to point to the inactive
> schema.
>
> Sorry about the confusion.
> >
> > From: "Khedr, Waleed" <Waleed.Khedr_at_FMR.COM>
> > Date: 2003/05/09 Fri PM 04:29:01 EDT
> > To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
> > Subject: RE: RE: Renaming tablespace by updating SYS.TS$
> >
> > Synonyms point to tables in schemas not Tablespaces.
> > My guess is your app is using synonyms that could point to one of two
> > schemas that are located in two different Tablespaces.
> >
> > By the way, you should know that the Tablespace name is also recorded in
> the
> > file headers, so I consider you lucky so far having no problems.
> >
> > Waleed
>
>
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.net
> --
> Author:
> INET: Jared.Still_at_radisys.com
>
> Fat City Network Services -- 858-538-5051 http://www.fatcity.com
> San Diego, California -- Mailing list and web hosting services
> ---------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Ryan
  INET: rgaffuri_at_cox.net

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).