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 220.127.116.11. 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
Today is SysAdmin day, don’t you know. Right up until last year, DBAs were included in this global movement to celebrate systems administrators. The Internet Wayback Machine gladly shows us how the site looked last year, clearly including DBAs right in the home page. This year? No mention of us!
Doug Burns of Doug’s Oracle Blog has volunteered to edit and publish Log Buffer #4. Thank you, Doug! We look forward to next Friday.
Welcome to the second weekly edition of Log Buffer, a series of “Carnival of the Vanities” blogs for DBAs. (I get to call it a series now that there’s more than one.)
A client asked me, “How can I move a table to another schema in Oracle?” The quick answer I gave him is, “not possible”. You have to rebuild it via “create table as select”. You might ask, justifiably, why would you want to do that anyway? His problem was that the application has been split into 2 parts, and he wanted to have separate schemas for each part, to ensure that there is no cross-schema table access.