Big Archive Log files
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 10 of 10

Thread: Big Archive Log files

  1. #1
    Join Date
    Aug 2000
    Location
    Chicago IL
    Posts
    586

    Unhappy

    Hi all,
    I turned on archive logging on to see if it works correctly but I noticed that every minutes i get 20 megs of archive file and I am going crazy trying to manage them. See every night at 12:00am I run hot backups on the box and I expect to clear up the mountpoint /arch1 4gig with a cron job but I need some guidance in tuining the archive logging. I dont want 20 megs a minute.
    pls advice asap

    "High Salaries = Happiness = Project Success."

  2. #2
    Join Date
    Mar 2000
    Location
    Atlanta, GA,USA
    Posts
    155
    Amount of archive logs depends on your database activity and a couple of parameters in init.ora Check for log_checkpoint_interval and log_checkpoint_timeout in init.ora
    F.e. on 1.6Tb database with high user activity I have up to 8 archive logs (10Mb each) per minute.

    Good luck!
    Sergey.

  3. #3
    Join Date
    Apr 2000
    Location
    Edison, NJ
    Posts
    759
    The thumb rule is to size the redolog files such that there would be 3-4 log switches per hour.

  4. #4
    Join Date
    Jun 2000
    Location
    Chennai/India
    Posts
    90
    Hi,
    Check the values of Log_Checkpoint_Interval and Log_Checkpoint_Timeout and set them appropriately. If still the problem persists, then you may have to check your transactions.

    Regards
    Ganesh .R
    A Winner never Quits, A Quitter never Wins
    Ganesh .R

  5. #5
    Join Date
    Aug 2000
    Location
    Chicago IL
    Posts
    586
    log_checkpoint_interval
    41000

    log_checkpoint_timeout
    0

    log_checkpoints_to_alert
    FALSE

    Hello. I have no redo in the morning because its a hybrid database.
    Please suggest new values for me.
    thanks
    "High Salaries = Happiness = Project Success."

  6. #6
    Join Date
    Aug 2000
    Location
    Chicago IL
    Posts
    586
    i have 4 groups with 20meg 2 members.

    Jigar
    "High Salaries = Happiness = Project Success."

  7. #7
    Join Date
    Oct 2000
    Location
    Cambridge, MA (Boston)
    Posts
    144
    you can't do much about the volume of redo info you generate. you'll generate whatever is needed by the users. the values of Log_Checkpoint_Interval and Log_Checkpoint_Timeout will not affect the amount generated nor how many redo logs you use. these parameters only affect checkpoints, not logswitches. you can limit some operations' redo information with NOLOGGING (or UNRECOVERABLE) but concern about redo generation is a REALLY bad reason to use these clauses.

    whether or not you run in archivelog mode, you should not turn over 60 redo logs/hour. increase the size of your redo logs (look at ALTER DATABASE ADD LOGFILE and then ALTER DATABASE DROP LOGFILE; use in conjunction with V$LOG and V$LOGFILE). be careful when managing redolog files in the operating system.

    d.

  8. #8
    Join Date
    Apr 2001
    Posts
    11
    check the size of your REDO logs - if they're too small, they fill up fast - each time they fill up a log switch is required. Each log switch generates an archive file.
    carl

  9. #9
    Join Date
    Mar 2000
    Location
    Chennai.Tamilnadu.India.
    Posts
    658

    jlakhani

    Dear jlakhani, 15th April 2001 15:11 hrs chennai

    I would like to know the DB size and nature of DB activity etc.

    As DBAtrix has said there is much can be done with the prameters you have provided.

    The only thing you can do is using NOLOGGING options for some transactions.

    Cheers

    Padmam
    Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it

  10. #10
    Join Date
    Aug 2000
    Location
    Chicago IL
    Posts
    586

    Exclamation

    hello,.....padmam...db size is about 30 gig. its an oltp system.
    I currently have 4 groups with 20 megs / member.

    shall i increase the memberst o 50 megs? Why whould I use nologging. BEcause i needt to be able to recover if my db crashes thats why I have archiving....
    "High Salaries = Happiness = Project Success."

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width