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.
I was looking for known issues under 10.2.0.2 (which are notoriously hard to find by searching MetaLink) and came across this note that mentioned 188.8.131.52. Looking up patch number 4547809 on Oracle’s FTP site (use your MetaLink credentials to log in), I see that it was released for Windows 32/64-bit, HP/UX 64-bit, and MVS (!) overnight:
Mike Kruckenberg has published the sixth edition of Log Buffer. Excellent post Mike, thanks!
Welcome to the fifth edition of Log Buffer. There’s lots to cover this week, so here goes.
Recently, I was doing some performance analysis for one of our clients, using STATSPACK and found that they were not using a consistent method for control. STATSPACK was installed on most instances but some instances had scheduled cron jobs for STATSPACK gathering, while others had dba_jobs. In addition, there was no cleanup implemented for some of the instances. This situation led me to think about finding a consistent, integrated and simple way of setting up and configuring STATSPACK.
Log Buffer #4: A Carnival of the Vanities for DBAs