Did anyone else notice this interesting e-week article titled The Downside of Certification? It immediately reminded me of an article written by Pythian team lead and datawarehousing architect Rob Hamel titled “Get Down with OCP: Evaluating DBA Job Applicants in an OCP World”. What Rob noticed in 2004 was that certification can mask a certain type of incompetence from a casual technical evaluation process.
Tip of the hat to Eddie Awad who does some noticing and some digging to confirm that lnnvl(), a function that provides functionality similar to ANSI “Is Not True” and can be used to return boolean TRUE whenever the predicate to the function is either NULL or FALSE is now supported in 10GR2.
Here is an article I posted on the Oracle-L mailing list recently. Much to my surprise, people liked it enough that they asked to see it here, too.
This was written in response to the question: “How do you edit an SPFILE?”
I skipped the general session but heard there was talk about Oracle unlimited support. Basically someone else summarized it as Oracle will take your money as long as you want to give it to them. So no more “de-supported” products. Of course, old products will not get bug fixes unless you really really really pay for it.
Good luck to acquaintances (dare I say friends? we have never met in person!) of mine Jonathan Lewis and Doug Burns who are presenting on April 27th at the UKOUG Northern Server Technology Day.
After I actually woke up I found myself attending a session about LogMiner by Chet Watmough. Log Miner in my opinion is a vastly under-used utility. It has such great versatility. Chet showed some techniques to add additional logging. By inserting the client info information into a dummy table, just to produce a record in the redo stream, he can identify who did what.
So I made my decision and went to “RAC & ASM best practices” presented by Kirk McGowan of Oracle. I wanted to see how far the documentation / common sense was from what will actually work. It wasnt that far from the docs, which is good. It means Oracle got it right.
Good luck to Pythian DBAs Christo Kutrosky and Babette Turner-Underwood who are presenting at Collaborate ’06 today and tomorrow. These are two outstanding presenters with deep technical knowledge reinforced with day-to-day use of the technology and I would encourage anyone to attend. If you attended the presentation, by all means post any feedback here!
I got in today and missed the General session … because I did not get here in time and still had to register. . . . I started the morning with an Oracle session on RAC. It was a two-part session and I did not have the patience to wait out the first half. It was on best practices and I was looking for something more technical.
I needed to change the undo_retention parameter in a 10gR2 database. Unfortunately I forgot whether the parameter was in seconds or minutes, and I wanted to see what the default was. So I open up the docs, go into the Reference guide and get the info I need from the top few lines. I wanted to set undo_retention to some large value in order to use flashback. So I decided to read if they were any notes about setting this too large. I started reading the notes. I’ve read this in the past, so didn’t expect anything new. Then I read the following: “For fixed-size undo tablespaces, the system automatically tunes for the maximum possible undo” What? Fixed size undo vs autoextend undo ? That’s new!