One of the things I love about my career (Oracle DataBase Administrator) , is how fragile it is on a day in and day out basis. I can say with certainty that every day I turn on my laptop to start working can be my last day working as a DBA. This is not because…
This is a short blog post on how one can prove that a particular partition of the table or index is accessed by a specific query.
Like many previous IOUG/OAUG/Quest shows, Pythian will be in Denver next week!
There’s a rare event happening next week: All three of Pythian’s Oracle Apps tech leads will be in the same place. Vasu Balla, Maris Elsins, and recently-minted Oracle Ace Director Yury Velikanov will all be at Collab 13 this year. Since we’re a globally distributed, round-the-clock team, this is not something that can happen very often.
It is less than a week before the Collaborate 2013 conference. Most of us are busy putting together our individual agendas for what is shaping up to be a very exciting week. There are so many interesting sessions to choose from! Conference organizers kindly introduced a Show Planner to make planning a bit easier, but in this blog post, I will share with you how I created my agenda for Collaborate.
First, the most important advice I can give you is to relax and have FUN!
This is a very short blog post to share a good news I learned last week at the great New Zealand Oracle User Group 2013 conference. During a keynote Tom Kyte mentioned that Oracle is going to introduce a Temporary Undo.
This is the second article in a series about internals and performance of concurrent managers. In this post, we’ll take a look at three important settings that affect the performance of the concurrent managers: number of processes, “sleep seconds”, and “cache size”. This article might be a bit on the theoretical side, but it should provide a good understanding of how these settings actually affect the behavior and performance of concurrent managers.
How to resolve unusual situation where Oracle was writing trace files into the user directory instead of the usual oracle diagnostic destinations.
When you set sizes for areas of the SGA (e.g. large_pool_size or java_pool_size) you might often see Oracle has used different and sometimes much larger values, this post explains some of the reasons why this might happen.