This is exactly what we do for one of our databases which had a similar
requirement, works great, but the offlining of the tablespaces can take a
bit of time as the buffer cache has to be cleared out for the tablespaces
being offlined. I've found multiple parallel export/imports can be faster.

Mike
[Email Address Removed] Original Message -----
From: "Ganesh Raja" <[Email Address Removed] "LazyDBA.com Discussion" <[Email Address Removed] Friday, November 28, 2003 10:03 AM
Subject: RE: Two scenarios for backup and recovery --> which one is better?


> When u move a Database from one mode to the Other the Backups Taken
> prior to that are made invalid.
>
> Deletig your Archiving is Doom One day ...
>
> My idea...
>
> See if you can create a Spare Instances that does not run on ArchiveLog
> Mode.. Refresh your DW on that Instance and use TTS to Move TBS from
> there to the Originnal Instance..
>
> My $0.02...
>
>
>
> Regards,
> Ganesh R
> HP : (+65)9067-8474
> Mail : ganesh.[Email Address Removed] ==========================================
> All Opinions expressed are my own and do
> not in anyway reflect those of my employer
> ==========================================
>
>
> -----Original Message-----
> From: Andrew.[Email Address Removed] [mailto:Andrew.[Email Address Removed] Sent: Friday, November 28, 2003 22:57 PM
> To: LazyDBA.com Discussion
> Subject: Two scenarios for backup and recovery --> which one is better?
>
>
> We are in the process of creating backup and recovery strategy and we
> consider two approaches.
>
> Environment: Oracle 9.2, on Win2k. 2.5 GB data warehouse is refreshed
> (dropped/truncated) every night. . One table space (SPACE1) is not
> refreshed nightly and its data is added/changed everyday. We need
> ARCHIVING for this table space. The refresh of the DB takes about 3h
> and generates 9GB of archive logs. Our recovery time should not exceed
> 1h.
>
> Here are the two backup approaches we consider:
>
> 1) Every night we shutdown the DB and bring it up in NOARCHIVE mode.
> Then we load the DB. After the load is finished we make cold backup and
> turn the ARCHIVE on. ARCHIVE is necessary to prevent from data loss in
> table space SPACE1 that is updated during the day.
> - Pluses -- Turning off archiving makes the refresh faster. We do
> not
> have issues with space management (9GB of possible redo logs).
> - Minuses -- Shutting down Db every night might be an issue?????
>
> 2) The DB is in Archive mode all the time. After every data refresh
> we
> make hot backup of the DB and delete archive logs prior to hot backup.
> - Pluses ? We do not shutdown the DB every night.
> - Minuses ? We have to make sure the HD is not filled up with archive
> logs (space is a concern for us). Nightly data refresh takes longer.
>
> We are interested to hear what would be your take on these two
> scenarios.
>
> Thank you.
>
>

Oracle LazyDBA home page