Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Re: Renaming tablespace by updating SYS.TS$
import/output, sqlloader is not doable. to much I/O we are talking about 100 gigabytes a day sometimes.
>
> From: "Daniel W. Fink" <optimaldba_at_yahoo.com>
> Date: 2003/05/09 Fri PM 01:42:42 EDT
> To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
> Subject: Re: Renaming tablespace by updating SYS.TS$
>
> If you are having to hack at the oracle data dictionary in order to use
> transportable tablespaces, you need to rethink the process. Based upon
> the 0 downtime requirement, you need to propose an alternate solution,
> like export/import, sql*loader, dblinks, etc.
>
> I went through this process recently. The development team was very good
> at resume building, so transportable tablespace was the 'best' option
> since it was new. They architected the process without ever once testing
> the actual mechanics. When we identified, via testing and research, that
> tts was not doable, we had to go back to the beginning.
>
> --
> Daniel W. Fink
> http://www.optimaldba.com
>
>
> rgaffuri_at_cox.net wrote:
>
> >Now I understand the process better. Im hoping someone has a better process.
> >
> >We have a staging database onsite. We need to transport tablespaces every day. Sometimes in the middle of the day to a remote production database. Therefore any downtime during transport is out of the question.
> >
> >1. So here is what we do. In our staging database. We rename the tablespace that will be transported to something of the form
> >
> ><name>_data, we then transport it and rename it back to its original name.
> >
> >2. On the production server we have two copies of the this tablespace.
> >
> ><name>_oldDate
> ><name>_currentDate
> >
> >3. We then import the new tablespace. When import is complete we have the synonyms that pointed to the old tablespace point to the new tablespace. We therefore have no downtime whatsoever. Downtime is only a few minutes, but we cannot have any downtime at all.
> >
> >We have tested this with in doubt queries(again no DML is performed) and found that if we switch the synonyms to the new tablespace during a query, Oracle is smart enough to not skip a beat and complete the query properly.
> >
> >anyone have a better solution? Renaming TS$ is risky. We pretty much follow a standard Datawarehouse publication process.
> >
> >
> >
>
>
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.net
> --
> Author: Daniel W. Fink
> INET: optimaldba_at_yahoo.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: <rgaffuri_at_cox.net 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).Received on Fri May 09 2003 - 13:07:35 CDT