Who is generating more archive logs




















It is taken from MOSC document but the example shown below is taken from our environment. I got to know the below topic when we had experienced the bad SQL query performance in one of our production environment during daily batch running time. Introduction The "cost-based optimizer CBO or just optimizer is the part of database software that determines the most efficient means of accessing the specified data or at least what it "calculates" as the most efficient. The optimizer determines which execution plan is most efficient by considering several sources of information, including query conditions, available access paths, statistics gathered for the system, and hints.

Some changes in those conditions may affect the calculations of the plan. May 01, Here we'll see how to find heavy or more cpu consumed sql query in oracle We are facing high CPU load on Linux servers daily at times. SID ,ss. Graham, February 11, - am UTC. That's a really helpful query Connor provided and definitely worth using but I feel it is also important to step back a bit and look at the situation from a more strategic overview.

What is the nature of your company's application? Do you have one database per application or does your database support several applications? Is the GB daily redo a recent thing or has it always been the case?

It's good to know what is "normal" for your system. Perhaps have a chat with your developers or business teams to see whether new or different functionality has been introduced recently, we've seen application updates here where redo and other system activity has almost doubled overnight to give us a "new normal" after major application changes.

Does the size of your database also grow accordingly? Are more and more records being stored? If they're not so much then the redo could be generated by changes to current data rather than additions. Again, this could be business logic. It's a nice approach you've taken though to increase the sizes of the redo logs because very very frequent log switches can have a negative impact on performance, however it won't as you've seen change the total volume of redo.

Hi again, Thank you all for your prompt replies and comments. EXE M redo size 37 xxx xxxorcl Leave a comment Cancel reply Your email address will not be published. Please enter the details below. We will try our best for you We have more amazing posts. Try searching here.

We assure our best to meet up to your expectations. Your Feedback will help us. Your Feedback. Glad That You Liked It. Your Feedback will help us to improve.



0コメント

  • 1000 / 1000