Re: Turning ARCHIVELOGMODE off and on

Alton,

You can do this. However, if you are using SQL*Loader a somewhat easier path is available. You can use the UNRECOVERABLE option in DIRECT mode to avoid both Indexes and Redo Logs (hence Archiving). Since you are migrating from Paradox, I would guess (and hope) you are dumping from Paradox in SQL*Load-able format.

You will still need to backup the database after a load because the database is essentially unrecoverable. There are also some constraints on concurrent users - but I would hope a big load is done without other on the database anyway, if possible.

This would basically avoid having to faff around with the archivelog mode.

BTW, in your method you should perform the las backup _after_ you have re-enabled archivelogmode so that any recovery to post-load has logs archived.

>We are gradually migrating database applications from Paradox to Oracle
>7.3. The trouble is: I don't want the database to be running in
>ARCHIVELOGMODE all the time. When I'm about to load a lot of data into
>Oracle, I don't want to create a lot of redo entries. Is it possible
>to:
>
>--Run in ARCHIVELOGMODE for a time;
>--Take the whole database off line;
>--Perform a full physical backup;
>--Bring the database back on line;
>--Alter the system to run with ARCHIVELOGMODE off;
>--Load my data;
>--Take the whole database off line again;
>--Perform another full physical backup;
>--Bring the database back on line, this time with ARCHIVELOGMODE on?
>
>I realize that any redo log files from the earlier ARCHIVELOGMODE period
>will be rendered useless. Even so, is this an OK idea?
>
>Alton Chinn
>SF Planning Dept
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
Received on Sat Jul 24 1999 - 07:14:22 CDT