This discussion is archived
4 Replies Latest reply: Sep 10, 2012 11:34 PM by User470870-OC RSS

Archive log management

User470870-OC Newbie
Currently Being Moderated
Helllo...

Database version : 11.0.1.7
Applications : 12.1.3

We have a below settings for archivelog management
Set only one archive dest but defined as 10 destinations can be enabled for archive logs.
Is this correct..?
As we are facing slowness when logswitch occurs and log_archive_max_processes are set to 4.

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_config string
log_archive_dest string
log_archive_dest_1 string LOCATION=/u03/PROD/Archive
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0

Regards..
  • 1. Re: Archive log management
    KuljeetPalSingh Guru
    Currently Being Moderated
    Set only one archive dest but defined as 10 destinations can be enabled for archive logs.
    looks normal,as by default log_archive_dest_state_* are enabled.
    As we are facing slowness when logswitch occurs and log_archive_max_processes are set to 4.
    whats the size of your redolog...and any special AWT top wait event during slowness.
    is logswitch happening very frequent or after 10-15 mins as it could be possible due to slow disk as it has to create archivelog on disk if its running on archivelog mode.
  • 2. Re: Archive log management
    User470870-OC Newbie
    Currently Being Moderated
    Hi..

    Thanks

    Enabled 10 archive destinations but set only one path for archive log files to be created by log_archive_dest_state_1 = "LOCATION=/u03/PROD/Archive"
    I think if i want to define only one archive destination, log_archive_dest is enough right..? correct me if i'm wrong.

    Any difference between log_archive_dest_state_1 and log_archive_dest?
    And there are 8 redo log goups and log_archive_max_processes=4, is it causing slowness because of less archive_processes..?
    Can we increase it to 8 instead of 4.

    Thanks..
  • 3. Re: Archive log management
    KuljeetPalSingh Guru
    Currently Being Moderated
    955685 wrote:
    Hi..

    Thanks

    Enabled 10 archive destinations but set only one path for archive log files to be created by log_archive_dest_state_1 = "LOCATION=/u03/PROD/Archive"
    I think if i want to define only one archive destination, log_archive_dest is enough right..? correct me if i'm wrong.
    yes and you've already setup one destination log_archive_dest_state_1 which is ok.

    >
    Any difference between log_archive_dest_state_1 and log_archive_dest?
    For Enterprise Edition users, LOG_ARCHIVE_DEST parameter has been deprecated in favor of the LOG_ARCHIVE_DEST_n parameters.

    http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams099.htm
    And there are 8 redo log goups and log_archive_max_processes=4, is it causing slowness because of less archive_processes..?
    Can we increase it to 8 instead of 4.
    not really required ,
    Read this
    There is usually no need specify this initialization parameter or to change its default value, because the database starts additional archiver processes (ARCn) as needed to ensure that the automatic processing of filled redo log files does not fall behind.
    http://docs.oracle.com/cd/B19306_01/server.102/b14231/archredo.htm#i1007359

    switch is happening because of dml activity going on database during this time which generated redo data. so slowness could be due to some particular process which are doing transaction at database level and AWR / ASH report will give you clear picture on this.
  • 4. Re: Archive log management
    User470870-OC Newbie
    Currently Being Moderated
    Thanks for the valuable reply...

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points