RE: Archivelog

Hi Varad,
There is something more (as always)...
Here is what you need to do (you may already know most (or some) of these):

1. create a directory on the system to hold archived logs. You will also need to have a mechanism to copy these to a safer place (tape, for example) and remove copied logs from this directory to make room for more. If this directory gets full, and if no more logs can be written to it, then your database will hang.
2. modifiy your init.ora file to include parameters: log_archive_start = true ## This is to start the archive process when the db starts log_archive_dest = <directory mentioned above to which Oracle can write to> log_archive_format=<naming convention for the archived log files>
3. shutdown the database
4. starup the database in mount mode
5. issue command : 'alter database archivelog;' to begin the process of archiving logs
6. alter database open
7. you can then confirm if everything looks okay by issuing command: 'archive log list'
8. try switching log files manually to make sure the archive logs are being created in the 'log_archive_dest' directory.

Now you can take an on-line (hot) backup of your database.. along with all the archived log files...

HTH..
- Kirti

> -----Original Message-----
> From: Rajan Varad G [SMTP:vrajan_at_hsc.hac.com]
> Sent: Wednesday, June 21, 2000 12:44 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Archivelog
>
> I wanted to turn the Archivelog mode on and if I change the parameter
> in the init.ora file and issue the SQL command
> "ALTER DATABASE ARCHIVELOG', is it enough or do I need to do something
> more. I appreciate your replies. Thanks.
>
> ..Varad << File: Card for Rajan Varad G >>
Received on Wed Jun 21 2000 - 12:57:16 CDT