Redo Logs sizes!
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: Redo Logs sizes!

  1. #1
    Join Date
    Feb 2001
    Posts
    286
    Hi all!

    Working on Oracle v8i with D2K Forms & Reports v6i OS as win2k.

    How are you!

    Query:

    1.For a shared mode(MTS) Database as we have at present for a 3GB database,My redo Log Files are of the following sizes:


    SQL> select GROUP#,THREAD#,SEQUENCE#,BYTES,MEMBERS,STATUS
    2 from v$log;

    GROUP# THREAD# SEQUENCE# BYTES MEMBERS STATUS
    ---------- ---------- ---------- ---------- ---------- ----------------
    1 1 56047 1048576 1 INACTIVE
    2 1 56048 1048576 1 ACTIVE
    3 1 56049 1048576 1 CURRENT

    SQL> select * from v$logfile;

    GROUP# STATUS
    ---------- -------
    MEMBER
    --------------------------------------------------------------------------------
    1
    D:\ORACLE\ORADATA\PVPL\REDO03.LOG

    2
    D:\ORACLE\ORADATA\PVPL\REDO02.LOG

    3
    D:\ORACLE\ORADATA\PVPL\REDO01.LOG


    Please suggest whether the above sizes for redo log Files are ok for a 3GB database or should I increase the sizes as
    well as members for redo log Groups to increase Performance!


    Thanks & Regards,

    Amit.
    Oracle DBA (OCP) v8i,v9i

  2. #2
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    The size of the database and the size of the redo logs are not directly corelated. For your 3GB database, three log groups of 1M might be just right, way too small or way too large. The same could be said for 100K or 500M log sizes on 3GB database.

    It is not the size of the database, it is the amount of redo information generated in a unit of time that matters.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  3. #3
    Join Date
    Jan 2002
    Location
    Netherlands
    Posts
    1,587
    Correct. Look at it this way it's a huge database but there are a lot of tables which are being filed in as history(purchase orders/maintenance jobs/etc etc) and in a period of time it'll accumulate/size up but will necessarily not be queried.
    So it might just be ok.
    Tarry Singh
    I'm a JOLE(JavaOracleLinuxEnthusiast)
    TarryBlogging
    --- Everything was meant to be---

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