Indeed, while the technique we discuss here is basic, it gives a good overview and is very easy to use. So let get focused… We will use iostat utility. There is much to say about IO monitoring and interpreting results. Perhaps this is only the first of a series of posts about IO statistics. At Pythian we often come across different environments with specific characteristics and various requirements that our clients have. So stay tune — more to come.
Welcome to the tenth edition of Log Buffer, the weekly compendium of blogs for DBAs. Let’s dive right in.
Over the Top Tales from the Trenches: Bringing order to the chaos of every day DBA life.
Typically, we monitor the v$datafile to ensure there are no NOLOGGING operations that will break our standby database. So it is important that we confirm that this mechanism actually works. ut for some reason, it is showing nothing under v$datafile for the YESLOG tablespace. I know this operation will break the standby database (because of a break in archive-log activity). I am just not sure how to confirm in the data dictionary.
The ninth edition of Log Buffer, the weekly review of database blogs, is now available at Daniel Schneller’s Blog.
In this second part , I will outline more details of a new STATSPACK methodology. As I mentioned in previous part , the statspack_setting table is a bridge between the user and Oracle’s STATSPACK.
he scinitllating eighth edition of Log Buffer is published, courtesy Craig Mullins of dbazine.com.
This first installment will deal with the biggest contributor to bad application design — the dreaded bad query. I’ve actually had busy systems crash because a developer unleashed a query that performed a full tablescan too many.
Welcome to the 7th edition of Log Buffer. As always, there’s lots to take in, and in fact, I cut more than I covered this week. Maybe I should make LB a little longer?
I just read this excellent review by Matt Asay of an excellent interview by Guy Kawasaki (of garage.com and apple fame) of MySQL CEO Marten Mickos.