Switch redo logs hourly to provide point-in-time?

Hi All,
Oracle 11G on Windows 2008 R2
I am learning the details of managing backups/restores and want to be able to provide a good point-in-time capability in case of a disaster. Is it good practice to schedule an hourly job that does ALTER SYSTEM SWITCH LOGFILE; ? Does this cause the redo log to be archived every hour so if I needed to restore, I know that I can at least restore to the previous hour (using the archive logs) and before?
Thanks in advance

Aman beat me to what I was going to say.  I'll just add a couple of points:
This really needs to established in concert with management, normally called an SLA (Service Level Agreement).  In a nutshell, you define what kinds of failures you allow for, how quickly recoveries or other procedures such as failovers will happen, what uptime is required, and so forth.  Of course, in reality many places won't spend the dollars to properly evaluate these things unless they are about to spend millions on an upgrade, so for ordinary places with ordinary business software the 15-30 minute rule covers many common recovery situations as a first approximation.  Simply asking management often gets a wrong or inadequate answer.
Personally, I find there are times of large loads or updates, so I size redo to handle those by testing, then use the lag target to have a reasonable time switch during normal operations.  This winds up requiring large redo, but archived redo is much smaller, except of course during the heavy times.  The same with undo also; yearly operations or massive updates require large undo, so just keep it around rather than trying to size it under the gun when it fails the next year.  Redo is a critical resource, and may benefit from special filesystem handling, depending on your storage hardware.
Job number one for a DBA is to not lose data, so recovery skills are critical, to the point of sometimes having to push management to do things right when they don't understand the value of their data.

Similar Messages

  • Redo Log Switch 결과...

    환경 : 8.1.7.3.0 (no archive log 모드)
    log_checkpoint_timeout = 0
    log_checkpoint_interval = 999999999
    redo log size = 200M
    현재 check point는 log switch 상태에서만 가능하도록 설정된 것 같습니다.
    거래량이 적어서 그런지 log switch는 30시간 주기입니다.
    제가 실행한 것은 아래 4번째 로그가 current일때
    alter system checkpoint를 하고 조금 있다가..
    alter system switch logfile를 하여 1번째가 current가 된 상황입니다.
    3/16일 14시 까지도 계속 active상태입니다...
    1. 문제가 생긴건지요??? 도움부탁합니다...
    2. no archive log mode에서도 switch 주기를 줄이는 것이 복구에 도움이 되나요...?
    ===========================================
    STATUS , FIRST_CHANGE#,FIRST_TIME
    CURRENT , 8846777646687,2007-03-15 16:57:55
    INACTIVE, 8846777587798,2007-03-14 10:34:40
    INACTIVE, 8846777609448,2007-03-14 17:17:38
    ACTIVE , 8846777643690,2007-03-15 16:01:22

    no archivemode에서 정상복구를 바라는 것인지요?
    잘못된 정책이란 생각이 듭니다.
    no archive mode에서 v$log의 first_change# 중에 가장 작은 것
    이 v$recover_file의 change# 보다 크거나 같다면 복구불능입니다.
    배치작업이라도 있어서 log switch가 한번의 cycle을 돌게 되면 이전
    백업으로는 복구불능입니다. archive mode로 지금 바로 바꾸시지요..
    log_checkpoint_timeout은 checkpoint에 대한 timeout 시간값을
    지정하는 것입니다.
    LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.
    checkpoint는 아시는 바와 같이 데이터파일과
    리두로그 컨트롤파일의 SCN을 일치시키는 것입니다. 주요한 것은
    DBWR프로세스가 데이터파일에 write를 하겠구요.
    물론 checkpoint와 인스턴스 복구는 관련이 있습니다. checkpoint timeout을
    적당히주면 instance recovery에서 좀 더 빠르게 instance 복구후 DB가
    open되겠습니다. 만약 설정하신대로 하신다면 DB를 abort로
    내리고 open하게 되면
    instance recovery시에 더 많은 시간이 필요하겠습니다.
    게다가 트랜잭션으로 인한 log switch하는 시간이 30시간보다
    작다면 timeout을 준들 영향을 주지 않겠지요. redo log가 꽉
    차게 되면 log switch를 자동으로 하게 되는데 log switch를
    하기전에 checkpoint를 주게 되어 있으니까요.
    그런데 checkpoint와 물리적/논리적 복구와는 다른 개념입니다.
    checkpoint는 위에서 말씀드린 instance recovery와 관련이 있고
    물리적/논리적 복구에서는 archive file이 떨어져 있는가 current redo log가
    존재하는가에 따라서 복구가능여부를 결정되는 것이지요..
    그리고 ACTIVE 상태라는 것은 문서상의 정의에서는 archive mode일 경우
    archiving이 되는 중일 경우, 그리고 이 상태는 complete recovery시에 redo log
    적용시 필요한 정보가 있다는 것입니다.
    no archive mode에서 복구정책을 적용 하겠다는 것은 위험한 발상인 것 같습니다.
    물론 DSS시스템의 경우에는 이미 정책을 no archive mode로
    만들어두고 주말마다 offline backup을 하기도 합니다.
    하지만 DSS에서는 하루에 300번 이상의 log switch가 일어나는
    경우가 있을 정도이니 아무리 백업이 되어 있다 한들 완전복구는
    불능이겠지요. offline backup을 했을 때까지만 복구가 됩니다.
    $LOG
    This view contains log file information from the control files.
    Column Datatype Description
    GROUP#
    NUMBER
    Log group number
    THREAD#
    NUMBER
    Log thread number
    SEQUENCE#
    NUMBER
    Log sequence number
    BYTES
    NUMBER
    Size of the log (in bytes)
    MEMBERS
    NUMBER
    Number of members in the log group
    ARCHIVED
    VARCHAR2(3)
    Archive status (YES |NO)
    STATUS
    VARCHAR2(16)
    Log status:
    UNUSED - Online redo log has never been written to. This is the state of a redo log that was just added, or just after a RESETLOGS, when it is not the current redo log.
    CURRENT - Current redo log. This implies that the redo log is active. The redo log could be open or closed.
    ACTIVE - Log is active but is not the current log. It is needed for crash recovery. It may be in use for block recovery. It might or might not be archived.
    CLEARING - Log is being re-created as an empty log after an ALTER DATABASE CLEAR LOGFILE statement. After the log is cleared, the status changes to UNUSED.
    CLEARING_CURRENT - Current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch such as an I/O error writing the new log header.
    INACTIVE - Log is no longer needed for instance recovery. It may be in use for media recovery. It might or might not be archived.
    no archive mode에서도 복구하는 여러가지 방법들이 있기는 합니다.
    예를들어 current redo log가 깨졌을 때에 recovery 방법이라던지
    등등이 문서에 있긴하지요. 하지만 no archivemode에서 백업을 붓고
    복구하는 방법은 찾아보기 힘드실 것입니다. 위에서도 말씀드렸듯이
    no archive mode에서
    v$recover_file의 CHANGE# > v$logl의 minimum FIRST_CHANGE# 이면 데이터파일은 복구가능합니다.
    그러나 CHANGE# <= minimum FIRST_CHANGE# 이면 복구 불가능합니
    다. 그러니 백업을 붓고 복구를 하는 방법에 대한 문서는 거의
    찾기 힘듭니다. advance 방법에 대한 문서에서만 adjust_scn을 쓴다던지 하는 등이 나와있을 뿐입니다.
    글 수정:
    민천사(민연홍)
    아무래도 졸면서 썼나봅니다.;;
    interval과 timeout은 엄연히 다른데요. 왜 timeout과 interval을
    혼동했는지..;;
    LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.
    LOG_CHECKPOINT_TIMEOUT specifies (in seconds) the amount of time that has passed since the incremental checkpoint at the position where the last write to the redo log (sometimes called the tail of the log) occurred. This parameter also signifies that no buffer will remain dirty (in the cache) for more than integer seconds.

  • 10G redo log switchs with no activity

    We have been testing 8i to 10G migrations and two things I have noticed that are different bwteeen the 2 databases are:
    1) redo log switching occurring even though the database has no users and just sitting there. This is not happeniong in our 8i databases.
    2) trace files of format instance_m001_ and instance_m000_ in ../bdump. Our 8i bdump's normally do not have trc files unless a problem occurs.
    Is it normal for 10G to automatically switch redo logs with no activity and are these .trc files also normal? In general I get nervous with trc files. -quinn

    Still haven't figured out the redo log switches, they seem to be slowing down, but the excess trace files are apparently cuased by a bug and can be fixed with Patch 3432729.

  • Redo log content in NOARCHIVELOG mode

    I have several servers running Oracle 9i databases in NOARCHIVELOG mode. I know this means that the online redo logs are not archived. I have been tracing the Oracle log writer with truss, and only see I/O going to the Oracle control files. I see no I/O going to the online redo logs. Can someone point me to the Oracle documentation that discusses exactly what gets written to the online redo log files while in NOARCHIVELOG mode? Thanks in advance for any assistance.

    Try Oracle Concepts on
    http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96524.pdf

  • Polling on a practice for REDO logs

    I would like to do a poll on the below security practice because it seemed not commonly deployed. If this practice is done in your company for the core databases, could you please reply to my posting and state your industry, DBA strength and total number of employees? Will collate the results later.
    Previous posting 14/4/04:
    Can the archive and redo logs be maintained in a way such that no one administrator (sys ad or DBA) will have access to all copies of logs? This is to prevent any disgrunted party to delete the logs and render the point-in-time data recovery impossible. What is the most common way used to achieve this? Thanks for reply:-)
    (I am thinking of writing the logs to 2 servers, inwhich one server is fully owned and not accessible to the SysAd)

    Are you trying to simultaneously use the Data Guard Broker and issue commands in SQL*Plus?
    If so this does not work: Choose one tool and stick with it.

  • Purpose of ONLINE REDO LOG FILES - Media or Instance recovery or BOTH ?

    Hi
    Currently studying this topic for the 1z0-031 exam and am a little confused.
    my books (from instructor led class) say
    -redo logs are a mean to provide redo transactions in the event of a DATABASE recovery
    -redo log buffer gets flushed to redo log files to provide a recovery mechanism in case of MEDIA FAILURE
    Then it says
    -Online redo log files are used in a situation such as an INSTANCE FAILURE to recover uncommitted data which has not yet been written to the data files
    - online redo log files are used for RECOVERY only.
    Am i misunderstanding? Or are redo log files for both MEDIA and INSTANCE recovery? Or just INSTANCE ?
    confused....
    Amanjit

    Online Redo Log Files are used in a sense for both Media and Instance Recovery. If your database is in NoArchive Mode then you will only be able to use the Redo Log Files for instance recover. But if you are running in Archive Log Mode then Redo Log Files are archived and will allow you to recover from media failure.

  • Thread 1 advanced to log sequence (redo log)

    Hi All,
    db:oracle 10gR2(10.2.0.4)
    os:solaris10
    My alert log file shows following information all the time....can you please explain me whats going on??
    Mon Jan 30 01:40:30 2012
    Thread 1 advanced to log sequence 253305
    Current log# 2 seq# 253305 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 01:45:40 2012
    Thread 1 advanced to log sequence 253306
    Current log# 3 seq# 253306 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 01:51:21 2012
    Thread 1 advanced to log sequence 253307
    Current log# 1 seq# 253307 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 01:56:53 2012
    Thread 1 advanced to log sequence 253308
    Current log# 2 seq# 253308 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:01:57 2012
    Thread 1 advanced to log sequence 253309
    Current log# 3 seq# 253309 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 02:06:31 2012
    Thread 1 advanced to log sequence 253310
    Current log# 1 seq# 253310 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 02:11:37 2012
    Thread 1 advanced to log sequence 253311
    Current log# 2 seq# 253311 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:16:44 2012
    Thread 1 advanced to log sequence 253312
    Current log# 3 seq# 253312 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 02:21:51 2012
    Thread 1 advanced to log sequence 253313
    Current log# 1 seq# 253313 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 02:27:11 2012
    Thread 1 advanced to log sequence 253314
    Current log# 2 seq# 253314 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:32:31 2012
    Thread 1 advanced to log sequence 253315
    Current log# 3 seq# 253315 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 02:37:25 2012
    Thread 1 advanced to log sequence 253316
    Current log# 1 seq# 253316 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 02:42:15 2012
    Thread 1 advanced to log sequence 253317
    Current log# 2 seq# 253317 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:47:05 2012
    Thread 1 advanced to log sequence 253318
    Current log# 3 seq# 253318 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    I appreciate your response......
    thanks.

    This information shows that the log switch has occured.
    The LGWR writes the redo information from the redo log buffer to the online redo log file. When the current online redo log file fills, LGWR begins writing to the next available online redo log file. In the mean time, the ARC process archives the contents of the filled online redo log file (If the database is in archivelog mode. If its in noarchive mode, then the filled online redo log file would not be archived). These archives are given a unique log sequence number.
    In your case 253305, 253306..are the log sequence numbers.
    You can refer http://docs.oracle.com/cd/B10501_01/server.920/a96521/onlineredo.htm for a detailed information

  • What if all the redo logs of a database are lost

    I want to know how a database can be recovered if all the three redo logs are lost at the same time.
    Thanks,
    Prabhath.

    You will be able to find the detail procedures of this kind of recover here:
    Backup and Recovery Concepts Contents / Search / Index / PDF
    Backup and Recovery Documentation Online Roadmap Contents / Search / /
    Recovery Manager Quick Reference Contents / Search / / PDF
    Recovery Manager Reference Contents / Search / Index / PDF
    Recovery Manager User's Guide Contents / Search / Index / PDF
    http://otn.oracle.com/pls/db92/db92.docindex?remark=homepage
    if you are making backups to the database using RMAN the recover is easier.
    Joel Pérez

  • Redo log space requests and Enqueue Waits

    Hi all,
    I am seeing an increase on the Enqueue Waits and Redo Log Space Request from 58, 274 to 192, 1245 in two weeks time respectively.
    The DB is a production database and runs on an HP cluster with 4X1G ram and 550mghz cpu.
    There are four Redo Log files with 200M (2 members each)which I have increased to 400M over this past weekend.
    I have included below the memory structure details:
    Redo Log Summary
    Total System Global Area 1646094824 bytes
    Fixed Size 104936 bytes
    Variable Size 408989696 bytes
    Database Buffers 1228800000 bytes
    Redo Buffers 8200192 bytes
    My question is that, who do I stop it from growing further and passing the 1:5000 ratio ?
    At the moment the ratio is in the range of 1:186194.
    Your input is much appreciated.
    Cheers,
    Seyoum.

    Here is some information from Oracle's Peformance Tuning Guide.
    The V$SYSSTAT statistic redo log space requests indicates how many times a server process had to wait for space in the online redo log, not for space in the redo log buffer. A significant value for this statistic and the wait events should be used as an indication that checkpoints, DBWR, or archiver activity should be tuned, not LGWR. Increasing the size of log buffer does not help.

  • Redo log recovery

    Hi,
    How do I recover if all the three redo logs are lost at the same time.
    Thanks,
    Prabhath.

    In archivelog mode
    1.- Shutdown the database
    2.- Restore the last backup
    3.- ensure that all needed archives are available
    4.- Carry out a recover UNTIL CANCEL
    In noarchivelog mode
    1.- Shutdown the database
    2.- create new redo log groups
    3.- recover the database recreating the controlfile
    4.- Open the database in resetlogs
    You will be able to find the detail procedures of this kind of recover here:
    Backup and Recovery Concepts Contents / Search / Index / PDF
    Backup and Recovery Documentation Online Roadmap Contents / Search / /
    Recovery Manager Quick Reference Contents / Search / / PDF
    Recovery Manager Reference Contents / Search / Index / PDF
    Recovery Manager User's Guide Contents / Search / Index / PDF
    http://otn.oracle.com/pls/db92/db92.docindex?remark=homepage
    if you are making backups to the database using RMAN the recover is easier.
    Joel Pérez

  • Redo log switching

    11gR2
    Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
    Wanted to know what would be negative side of large redo logs?

    >
    11gR2
    Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
    Wanted to know what would be negative side of large redo logs?
    >
    Patience, grasshopper!
    If it ain't broke, don't fix it. So first make sure it is broken, or about to break.
    Unless you have an emergency on your hands you don't want to implement a change like that without careful examination of your current log file usage and history.
    You need to provide more information such as typical size of your log files, number of log groups, number of members in each group, log archive policy, etc.
    1. How often do these 'peak periods' occur? Do they occur fewer than 5 or 6 times a day? Or dozens of times?
    2. How long do they last? A few minutes? Or a few hours?
    3. What is the typical, non-peak rate of switches? This is really your base-line that you need to compare things to.
    4. What has the switch pattern been over the last few weeks or months?
    5. What has the growth in DB activity benn over the last few weeks or months? What do expect over the next few months?
    6. What is your goal in reducing the frequency of log switches?
    Basic negative sides include longer time to archive each log file (the fewer logs in each group the more impact here) and the length of time to recover in the event you need to. With large log files there is more for Oracle to wade through to find the relevant data for restoring the DB to a given point in time.
    Your suggestion of every 20 - 30 minutes means 2 to 3 times per hour. If you currently switch 10 or 12 times per hour you are making a very big change.
    Although you don't want to 'tweak' the logs unnecessarily you also don't want to make such large changes.
    Everything in moderation. If your current switch rate is 10 or 12 times per hour you may want to first cut this to maybe 1/2 to 1/3: that is, to 4 or 5 time per hour. It all depends on the answers to questions like I ask above. If you post the answers to know if will be helpful to anyone trying to advise you.

  • What's the point of redo logs?

    Why does Oracle bother writing everything to redo logs? If it's going to write data changes to the disk, why not just write them once to the data files and be done with it? What's the point of doing it twice? And if it's a redundancy thing, why not mirror the data disks?

    Hemant K Chitale wrote:
    How would you backup a database while it is in use ? You can't lock all the datafiles to prevent writes to them. Yet, transactions may be updating different blocks in different datafiles even as the backup is in progress. Say your backup starts with datafile 1 (or even datafiles 1,2,3,4 in parallel) at time t0. By time t5, it has copied 20% of the datafile to tape or alternate disk backup location. Along comes a transaction that updates the 100th block (somewhere within the 10-11% range) of datafile 1 and also the 60th block of datafile 5. Meanwhile, the backup continues running, already having taken a prior image of the 100th block and not being aware that the block has been changed. At time t25 it completes datafile 1 (or datafiles 1,2,3,4) and starts backing up datafile 5. Now, when it copies the 60th block of datafile 5, it (the backup utility) doesn't know that this block is inconsistent with the backup image of the 100th block of datafile 1.
    Instead of 1 transaction imagine 100 or 1000 transactions occurring while the backup is running.
    Surely, Oracle must be able to regenerate a consistent image of the whole database when it is restored ?
    That is what the Redo stream provides. The Redo stream is written to Archivelogs so that it can be backed up -- no Archivelog file is "in flux" (particularly if you use RMAN to backup the Archivelogs as well !).
    Had Oracle been merely writing to the datafiles alone, without a Redo stream, there is no way it could recreate a consistent database -- whether after Crash Recovery OR after Media Recovery.Interesting point about how redo logs facilitate backups. So what you're saying is that the redo logs help keep the data in the actual data files in a consistent state by only writing full transactions to them at a time. Presumably Oracle will either write out the redo log data to the data files before a backup or will at least prevent the redo logs from writing to the data files during a backup. I always wondered how databases got around that problem of keeping the system available for writing during a backup. I wonder how SQL Server does it.
    Hemant K Chitale wrote:
    Now, approach this from another angle. A database consists of 10 or 100 or 500 datafiles. You have 10 or 100 or 1000 sessions issuing COMMITs to complete their transactions, which could be of 1 row or 100 rows or 1million rows, each transaction of a different size. Should the 1000 sessions be forced to wait while Oracle writes all those updated blocks to disk in different datafiles -- how many blocks can it write in "an instant" ?
    But what if Oracle manages to write much less information -- the bare minimum (called "change vectors") to re-play every transaction to a single file serially ? That would be much faster. Imagine writing to 500 datafiles concurrently, having to open the file, progess to the required block address and update the block, for each block changed in each file VERSUS writing much lesser information serially to a single file -- if the file is full, switch to another file, but keep writing serially.As to your second point, I don't really have a good enough understanding about the format of redo logs vs. the data files to follow you totally. Are you saying that it takes more time to write to the data files because you have to find the proper place in the B-Tree before you can write to it? And that doing that is slower than just opening the redo log and always appending new information to the very end? Maybe so, but it seems like all transactions having to write to a single redo log in serial would slow things down since there would be a ton of contention for one file. Whereas with the data files, you could potentially have several transactions writing to different files simultaneously (provided you hardware would support doing that). And it seems to me like a change vector would contain a lot more information than a field value, but, like I said, I'm not really familiar with the format.

  • Bottleneck when switching the redo log files.

    Hello All,
    I am using Oracle 11.2.0.3.
    The application team reported that they are facing slowness at certain time.
    I monitored the database and I found that at some switching of the redo log files (not always) I am facing a slowness at the application level.
    I have 2 threads since my database is RAC, each thread have 3 redo log groups multiplexed to the FRA, with size 300 MB each.
    Is there any way to optimize the switch of redo log files? knowing that my database is running in ARCHIVELOG mode.
    Regards,

    Hello Nikolay,
    Thanks for your input I am sharing with you the below information. I have 2 instances so I will provide the info from each instance
    Instance 1:
    Load Profile              Per Second    Per Transaction   Per Exec   Per Call
    ~~~~~~~~~~~~         ---------------    --------------- ---------- ----------
          DB Time(s):                4.9                0.0       0.00       0.00
           DB CPU(s):                1.1                0.0       0.00       0.00
           Redo size:        3,014,876.2            3,660.4
       Logical reads:           32,619.3               39.6
       Block changes:            7,969.0                9.7
      Physical reads:                0.2                0.0
    Physical writes:              164.0                0.2
          User calls:            7,955.4                9.7
              Parses:              288.9                0.4
         Hard parses:               96.0                0.1
    W/A MB processed:                0.2                0.0
              Logons:                0.9                0.0
            Executes:            2,909.4                3.5
           Rollbacks:                0.0                0.0            
    Instance 2:
    Load Profile              Per Second    Per Transaction   Per Exec   Per Call
    ~~~~~~~~~~~~         ---------------    --------------- ---------- ----------
          DB Time(s):                5.5                0.0       0.00       0.00
           DB CPU(s):                1.4                0.0       0.00       0.00
           Redo size:        3,527,737.9            3,705.7
       Logical reads:           29,916.5               31.4
       Block changes:            8,893.7                9.3
      Physical reads:                0.2                0.0
    Physical writes:              194.0                0.2
          User calls:            7,742.8                8.1
              Parses:              262.7                0.3
         Hard parses:               99.5                0.1
    W/A MB processed:                0.4                0.0
              Logons:                1.0                0.0
            Executes:            2,822.5                3.0
           Rollbacks:                0.0                0.0
        Transactions:              952.0
    Instance 1:
    Top 5 Timed Foreground Events
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                                               Avg
                                                              wait   % DB
    Event                                 Waits     Time(s)   (ms)   time Wait Class
    DB CPU                                            1,043          21.5
    log file sync                       815,334         915      1   18.9 Commit
    gc buffer busy acquire              323,759         600      2   12.4 Cluster
    gc current block busy               215,132         585      3   12.1 Cluster
    enq: TX - row lock contention        23,284         264     11    5.5 Applicatio
    Instance 2:
    Top 5 Timed Foreground Events
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                                               Avg
                                                              wait   % DB
    Event                                 Waits     Time(s)   (ms)   time Wait Class
    DB CPU                                            1,340          24.9
    log file sync                       942,962       1,125      1   20.9 Commit
    gc buffer busy acquire              377,812         594      2   11.0 Cluster
    gc current block busy               211,270         488      2    9.1 Cluster
    enq: TX - row lock contention        30,094         299     10    5.5 Applicatio
    Instance 1:
    Operating System Statistics        Snaps: 1016-1017
    -> *TIME statistic values are diffed.
       All others display actual values.  End Value is displayed if different
    -> ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
    Statistic                                  Value        End Value
    AVG_BUSY_TIME                             17,451
    AVG_IDLE_TIME                             81,268
    AVG_IOWAIT_TIME                                1
    AVG_SYS_TIME                               6,854
    AVG_USER_TIME                             10,548
    BUSY_TIME                                420,031
    IDLE_TIME                              1,951,741
    IOWAIT_TIME                                  288
    SYS_TIME                                 165,709
    USER_TIME                                254,322
    LOAD                                           3                6
    OS_CPU_WAIT_TIME                         523,000
    RSRC_MGR_CPU_WAIT_TIME                         0
    VM_IN_BYTES                              311,280
    VM_OUT_BYTES                          75,862,008
    PHYSICAL_MEMORY_BYTES             62,813,896,704
    NUM_CPUS                                      24
    NUM_CPU_CORES                                  6
    NUM_LCPUS                                     24
    NUM_VCPUS                                      6
    GLOBAL_RECEIVE_SIZE_MAX                4,194,304
    GLOBAL_SEND_SIZE_MAX                   4,194,304
    TCP_RECEIVE_SIZE_DEFAULT                  16,384
    TCP_RECEIVE_SIZE_MAX      9.2233720368547758E+18
    TCP_RECEIVE_SIZE_MIN                       4,096
    TCP_SEND_SIZE_DEFAULT                     16,384
    TCP_SEND_SIZE_MAX         9.2233720368547758E+18
    TCP_SEND_SIZE_MIN                          4,096
    Operating System Statistics - Detail  Snaps: 1016-101
    Snap Time           Load    %busy    %user     %sys    %idle  %iowait
    22-Aug 11:33:55      2.7      N/A      N/A      N/A      N/A      N/A
    22-Aug 11:50:23      6.2     17.7     10.7      7.0     82.3      0.0
    Instance 2:
    Operating System Statistics         Snaps: 1016-1017
    -> *TIME statistic values are diffed.
       All others display actual values.  End Value is displayed if different
    -> ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
    Statistic                                  Value        End Value
    AVG_BUSY_TIME                             11,823
    AVG_IDLE_TIME                             86,923
    AVG_IOWAIT_TIME                                0
    AVG_SYS_TIME                               4,791
    AVG_USER_TIME                              6,991
    BUSY_TIME                                475,210
    IDLE_TIME                              3,479,382
    IOWAIT_TIME                                  410
    SYS_TIME                                 193,602
    USER_TIME                                281,608
    LOAD                                           3                6
    OS_CPU_WAIT_TIME                         615,400
    RSRC_MGR_CPU_WAIT_TIME                         0
    VM_IN_BYTES                               16,360
    VM_OUT_BYTES                          72,699,920
    PHYSICAL_MEMORY_BYTES             62,813,896,704
    NUM_CPUS                                      40
    NUM_CPU_CORES                                 10
    NUM_LCPUS                                     40
    NUM_VCPUS                                     10
    GLOBAL_RECEIVE_SIZE_MAX                4,194,304
    GLOBAL_SEND_SIZE_MAX                   4,194,304
    TCP_RECEIVE_SIZE_DEFAULT                  16,384
    TCP_RECEIVE_SIZE_MAX      9.2233720368547758E+18
    TCP_RECEIVE_SIZE_MIN                       4,096
    TCP_SEND_SIZE_DEFAULT                     16,384
    TCP_SEND_SIZE_MAX         9.2233720368547758E+18
    TCP_SEND_SIZE_MIN                          4,096
    Operating System Statistics - Detail Snaps: 1016-101
    Snap Time           Load    %busy    %user     %sys    %idle  %iowait
    22-Aug 11:33:55      2.6      N/A      N/A      N/A      N/A      N/A
    22-Aug 11:50:23      5.6     12.0      7.1      4.9     88.0      0.0
              -------------------------------------------------------------

  • Redo Log Files - more than 12 per hour

    Hello @all,
    I have a problem with my redo log files. I get more than 12 switches per Hour. I have 3 Files with 5oM size. I increased the sitz to 15o M, but
    I still have 12 switches per hour.
    Do anyone know, what I did wrong?
    Database:
    Oracle 9i
    Thanks
    Martin

    user9528362 wrote:
    Hello @all,
    yes I know, that 3 switches per hour are perfekt, but I had increased the Size from 5o M to 15oM already and the amount from switches, are not reduced.
    So there must be something else, that causes the log switches.Martin,
    As I said somewhere above too, 150meg is a tiny size if you are managing a production db. I have already mentioned that make your log file size to at least 500meg and than check. As for the high redo activity, only you can confirm that whether this has been started from now only or was happening before too? In anycase, for an active oltp, 500 to 1gb of redo log file size should be okay.
    For the extra redo generation, you have been given link for mining log files using logminer. Try using it to see what is causing extra redo.
    HTH
    Aman....

  • T is frequently switching the redo log files within 5min approx..

    i am facing frequent switching of redo logs within 5minutes
    can you please tell how to resolve
    thanks for help

    Hi,
    I found this:
    More frequent log switches may result in decreased performance. If your redo logs switches so faster Oracle will stop processing until the checkpoint completes successfully. Generally it is recommended to size your redo log file in a way that Oracle performs a log switch every 15 to 30 minutes.
    A recommended approach is to
    Query V$LOG view to determine the current size of the redo log members.
    Record the number of log switches per hour.
    Increase the log file size so that Oracle switches at the recommended rate of one switch per 15 to 30 minutes.
    You can also check messages in the alert log in order to determine how fast Oracle is filling and switching logs. Suppose if your database redo log file size is set to 1MB. It means that Oracle switches the logs every 1 minute. So you will need to increase the size of redo log file to 30MB so that Oracle switches per 30 minutes.
    It is also recommended to ensure that your online redo log files do not switch too often during high activity time. Instead in the period of high activity it should switch less while it should switch enough times during the time of low processing workloads. Many database administrators create PL/SQL programs to ensure that the logs switch every 15 to 30 minutes during times when activity is low.
    Oracle ARCHIVE_LAG_TARGET can also be used to force a log switch after the specified amount of time elapses. The basic purpose of ARCHIVE_LAG_TARGET parameter is to control the amount of data that is lost and effectively increasing the availability of the standby database but many database administrators set ARCHIVE_LAG_TARGET parameter to make sure that the logs switch at regular intervals during lower activity time periods.
    You should also keep in mind that how the size of the online redo log files will affect the instance recovery. Remember the lesser the checkpoints are taken; the longer will be the instance recovery duration. You can decrease the instance recovery time by appropriately setting the LOG_CHECKPOINT_TIMEOUT, LOG_CHECKPOINT_INTERVAL and FAST_START_MTTR_TARGET parameters.

Maybe you are looking for

  • How to set a particular node selected in a JTree from within the model

    I have an adapter class that provides communication between my JTree and data model. My adapter class implements TreeModel, TreeExpansionListener, TreeSelectionListener and a listener for changes to my data model. My data model keeps reference to the

  • Parking document Using Special GL ,

    While parking document using special GL Indicator 'A " ,system Giving Eroor"  You have selected posting key with special gl Indicator down payment or bill of exchange ...Document parking not allowed for speial gl transaction type " bill of excahge" o

  • Time Machine - which old backups are deleted?

    Hi,      Apologies if the answer is obvious - just wanted a second opinion.      I'm backing up a 500GB MBP and a 2TB external to a 4TB Time Machine. If I complete a backup right now, can I be sure that everything on both drives is contained on the T

  • Mac, image order in photoshop--why can't Mac put things in order?

    Has anyone found this to be true/frustrating? You take many, many photos. You upload them to your Mac, open them up in Photoshop and they are out of order? When I'm shooting 6 frames a second, sometimes I would like to have the shots looked at in seq

  • Getting java.sql package.

    Hi, I need to download the java.sql package in order to connect to an Oracle database. Pl. suggest me a url where I could the above. (Searching sun's website yeilded only the doc files, ".html", which are for reference purpose. I am working on Apache