inconsistent archive log size
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: inconsistent archive log size

  1. #1
    Join Date
    Dec 2000
    Posts
    37
    I have an Oracle 8.0.4 database running on Windows NT. There are two redo log groups with size of 5M for each redo log. Ever since the creation of the database, there has been inconsistent archive logs generated. Some with the same size of redo logs, many of them with very small size like 500 bytes. It is a development database with very light activity.

    Is this a bug or did I miss something?

    log_checkpoint_interval = 10000
    log_buffer = 163840
    log_checkpoint_timeout = 1800
    log_archive_buffer = 4
    log_archive_buffer_size=127

    Any help will be greatly appreciated.

    Daphnny

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    There's two possiblities why you may be getting log files that are not close to 5M:
    1. an "alter system swith logfile" command is being executed.
    2. You have a redo log file out there that is not sized to 5M.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Dec 2000
    Posts
    37
    Originally posted by marist89
    There's two possiblities why you may be getting log files that are not close to 5M:
    1. an "alter system swith logfile" command is being executed.
    I have hot backup script running once a day with switch log command. But there are archived logs with different size at time other than the backup time.

    Originally posted by marist89
    2. You have a redo log file out there that is not sized to 5M.
    Here is the query v$log:
    13:21:38 SQL> select * from v$log;

    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
    --------- --------- --------- --------- --------- --- ----------------
    ------------- ---------
    3 1 26 5242880 2 YES INACTIVE
    627490 28-JUN-01
    4 1 27 5242880 2 NO CURRENT
    648478 29-JUN-01
    5 1 25 5242880 2 YES INACTIVE
    625038 28-JUN-01

    Notice the group# is 3, 4, 5. I added these three new groups after the creation of the database and dropped 2 old redo log groups.

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