Re: ARCHIVE LOG every 5 minut

Comments embedded.

Navs wrote:
> Hey as per the oracle ARCHIVE_LAG_TARGET limits the amount of data that
> can be lost and effectively increases the availability of the standby
> database by forcing a log switch after a user-specified time period
> elapses.
>

True enough, however all archived logs are 100 MB in size, indicating, to me, anyway, the redo logs are 100MB each and are filling every five minutes. Log switching on a schedule, although regular, will not likely produce equally sized archive log files unless the transaction volume is constant. And one can't expect every transaction to occupy the same space in the redo logs. My hunch is he's filling his redo logs every five minutes, in ARCHIVELOG mode.

> I don't think archive files gets generated due to setting above
> parameter.if ur using 9i and above please check the value
> fast_mttr_target parameter value
>

The operative phrase in your comment is 'I don't think', which is apparent from your assessment of the situation and the understanding, or lack thereof, of the topic upon which you chose to comment. Any setting/process which causes a log switch automatically generates archivelogs when in ARCHIVELOG mode with the proper init.ora parameters set. (Of course, if the database is in ARCHIVELOG mode and log_archive_start is FALSE in the init.ora then the redo logs fill and the database halts when all available redo logs have been used, in wait for manual archiving to commence.) How you arrived at your conclusion ("I don't think archive files gets generated due to setting above parameter.") is a mystery. Possibly in the same manner as offering the non-existent parameter fast_mttr_target; fast_start_mttr_target is, I believe, the parameter you intended to provide. Although, I am at a loss to explain WHY you believe setting this parameter limits the amount of redo; log_checkpoint_timeout and log_checkpoint_interval are provided to limit the amount of redo, and they do so in the following ways:

log_checkpoint_interval, specified in redo blocks: Limits the number of redo blocks that can exist between the most recent checkpoint and the end of the log.

log_checkpoint_timeout, specified in seconds: At most, n seconds worth of logging activity can occur between the most recent checkpoint position and the last block written to the redo log.

Neither creates a log switch, so neither will generate more archivelogs when set. More checkpoints, but not more archivelogs.

> Regards
> Naveen

I still stand on my original assessment, stated above, that the OP has a situation where he has 100 MB redo logs, his database is in ARCHIVELOG mode and the redo logs are being filled every five minutes. The consistency of the archivelog file size leads me to this conclusion.

David Fitzjarrell Received on Mon Jun 27 2005 - 14:40:04 CDT