Re: from Non-Archive-Mode to Archive-Mode

2003-01-21 Thread Rajesh . Rao
recipients of list ORACLE-L [EMAIL PROTECTED] tmail.com cc: Sent by: Subject: Re: from Non-Archive-Mode to Archive-Mode

Re: from Non-Archive-Mode to Archive-Mode

2003-01-21 Thread Arup Nanda
ORACLE-L [EMAIL PROTECTED] tmail.com cc: Sent by: Subject: Re: from Non-Archive-Mode to Archive-Mode root@fatcity. com January 17, 2003 05:54 PM

Re: from Non-Archive-Mode to Archive-Mode

2003-01-17 Thread Arup Nanda
Murat, The estimate of amount of space for archive logs come from your redo log switch. If you have placed the init.ora parameter log_checkpoints_to_alert set to TRUE, then your alert log file will have lines when the redo log group switch fom one to the other. That will give you a rough idea of

RE: from Non-Archive-Mode to Archive-Mode

2003-01-17 Thread Stephen Lee
It depends on how much data is changed in the database. If there is no data manipulation, then you need very little archive space (just enough for the online logs when you run a backup). Look in the alert log to see how many log switches occur. I think this will give you a reasonable estimate

RE: from Non-Archive-Mode to Archive-Mode

2003-01-17 Thread Adams, Matthew (GECP, MABG, 088130)
Title: RE: from Non-Archive-Mode to Archive-Mode I personally use the following SQL to get a very rough estimate of how much archive space I'm going to need per day. select (num_logs*bytes )/(1024*1024) Megs per Day from (select ceil(avg(count(*))) num_logs from v$log_history lh group

Re: from Non-Archive-Mode to Archive-Mode

2003-01-17 Thread Rajesh . Rao
PROTECTED] tmail.com cc: Sent by: Subject: Re: from Non-Archive-Mode to Archive-Mode root@fatcity

Re: from Non-Archive-Mode to Archive-Mode

2003-01-17 Thread Arup Nanda
] To: "Multiple recipients of list ORACLE-L" [EMAIL PROTECTED] Sent: Friday, January 17, 2003 1:25 PM Subject: Re: from Non-Archive-Mode to Archive-Mode Arup, From your past replies to the list, I am surprised to hear you say this. "If you have placed the init.ora parameter log_checkpoin