Number 10? I only just finished Dirty Dozen #1. What’s going on here, then? Well, no one said I had to write them in any particular order! But, if you look at the posters, they are clearly numbered. Should someone else pick up the Dirty Dozen challenge, it will help them to see which ones…
Here is the perl script referred to by mysql-memory-usage-profile.
So, you just installed the Oracle 10g clusterware, you just ran root.sh and got an error, you just went to metalink Note:316583.1 or Note:387691.1 the given interface(s), “eth0″ is not public, public interfaces should be used to configure virtual IPs, it just failed, and now you are relying on Google to help you with what Metalink couldn’t. Well look no more, and here’s the solution.
I’m sure everyone has heard about TJX’s recent data security “problems”, if that’s what you can call “the largest known customer record theft of all time”. This eWeek article adds valuable details and analysis on how TJX had a data encryption.
Linux is a wonderful operating system. However there are a number of things that one needs to do to make sure it runs as efficiently as possible. Today, I would like to share one of them. It has to do with using ASM (Automatic Storage Manager) disks.
As promised, here is the first part of the series based on the MARSS posters — The Dirty Dozen — concerning the importance of clear communication between DBAs.
I tripped across this blog post by Jeff Smith and I have to say, this man has been scarred by what has to be the worst experience interacting with a DBA I have ever heard of. And Jeff, if this is not fiction, if this is real and you have really suffered this much – give us a call won’t you?
So you have swallowed the standby bait. You have used RMAN duplicate to create a sparkling new standby and things are looking rosy. Then, when you check the lag between the primary and standby (in MAXIMUM PERFORMANCE mode), you discover the standby is miles behind. Oracle (at least from 9iG) rides to the rescue again. The parameter ARCHIVE_LAG_TARGET tells Oracle to make sure to switch a log every n seconds.
In this new installment of Pythian Goodies Doug Burns discusses Parallel Basics. This video is a good introduction to using Oracle Parallel features and most importantly, what problems you may have with it.
Last week, we discovered a bug related to the rollback of the Java DST patch for 9206 on Linux x86. If you’re in the unfortunate position of needing to roll this patch back, you won’t be able to. When you rollback, you need to restore both of these files, and then do a create or replace java system. Otherwise you risk hitting a dreaded ORA-03114 End of file on communication channel. Those of you familiar with DST patching will have seen this, but for those who haven’t, here are the scripts you need to check for a successful Java implementation: