I have submitted an abstract for my new presentation about linux/unix memory and Oracle to the Rocky Mountain Oracle Users Group for the Training Days in Denver on February 14-15, 2007. I pilot tested it at the Ottawa Oracle User Group in June. The feedback was good and since then I have kept developing the presentation. Soon to be submitted for HotSos 2007.
Over-the-Top Tales from the Trenches: Bringing order to the chaos of every day DBA life.
IT programs only teach you the programming and software architecture perspective. In DBA work, even when scripting, you have to consider the data as a tool. I’ll show you what I mean.
Over-the-Top Tales from the Trenches: Bringing order to the chaos of every-day DBA life.
It looks like Oracle has started testing the 10.2.0.3 patchset. A preliminary list of bugs fixed is at in MetaLink note 391116.1. The “important” bug fixes are here.
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.
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.
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.
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.
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.