I just installed 3.1.1 Oracle VM server on my sandbox for training purposes and faced the same issue I did when installing versions 3.0.3 and 3.0.1. I quickly found a workaround that worked for me. But as a follow up, I decided to search though Google and MOS in order to see if there has been any good development in resolving the issue from others.
Geeks, freakazoids, nerds, dweebs, it’s that time of the year again: May 25th i.e., International Geek Pride Day!! Here are some snapshots of the Geeks at Pythian celebrating in style today.
Glamour from across the world is sparkling in the South of France, but even that has failed to eclipse the vivid aura of the database blogs from the realms of Oracle, SQL Server, and MySQL. This Log Buffer Edition covers this glamorous gala of innovation.
The purpose of this blog isn’t to show off the results of my presentation at Collaborate conference, but to inspire you (and maybe myself in the future) and give you additional motivation to never give up on your dreams if you truly believe in them.
As SLOB takes the IO testing on Oracle Instance level, you need to watch for several things before you declare official testing results. My suggestion is: Don’t take any result for granted. You need to assess those before stating that you are done.
If you are wondering what I have been busying myself with, this post explains it. As you may have noticed, I am still testing one of the Oracle systems using the SLOB framework and learning on my way. I ran several tests with the same parameters (Readers 24) and noticed that for one reason or another awr.txt reports different runtimes.
I was wondering why I was getting inconsistent runtimes for similar conditions. The answer to the mystery was very simple: The runit.sh script just generates awr.txt reports for the last and before last awr snapshots.
In this post I provide a step-by-step guide outlining how to generate databasemachine.xml file to be used with OEM 12c.
If you are interested in the topic of ODA performance but missed the webinar or if you want to hear it again, you can view our recording here. I also uploaded the slides to slideshare, so you can take a better look at our benchmark results and study our consolidation methods at your own pace.
I was presented with test results that showed that IN query was about 100 times faster than OR query. Where OR query took minutes to run, IN query took seconds! Okay, I said to myself, it is time to start digging. Here are my findings.
At work, we have a need for a little job daemon that would poll jobs and process them. But there is more than one type of job, so the solution that we need will have to be a little more complex. To get to my goal, I decided that I would have a generic Poller class. For each type of job to monitor and run, I will create a different object with parameters to tell it how often to poll, how to poll, and what to do with the stuff it polls. Sounds good? Perfect, then let’s go.