I got an error message trying to login at oracle.com saying my account was locked. There was a simple solution for this, all you need to do is to use “Forgot password” functionality – this will reset your password and unblock the account.
Many have expressed the deepest desire to see OPT_ESTIMATE documented, but that never happened. I’ve just troubleshot a problem and used this hint a lot during my “what if” scenario testing, and found this hint to be quite useful. Thus, I decided to document it here on the blog. I will come back and update this blog as I discover new parameters, and feel free to suggest what you’ve found in the comments. If you can, include an example to illustrate usage.
So how does an Oracle DBA go about learning MySQL?
Obviously you start by reading the docs. Specifically, I looked for the MySQL equivalent of the famous Oracle “Concepts Guide”.
Unfortunately, it doesn’t exist. I couldn’t find any similar overview of the architecture and the ideas behind the database. The first chapter of “High Performance MySQL” had a high level architecture review, which was useful but being just one chapter in a book, it lacked many of the details I wanted to learn. Peter Zaitsev’s “InnoDB Architecture” presentation had the kind of information I needed – but covered just InnoDB.
I recently reformatted my laptop with the latest Ubuntu LTS release, 10.04, aka Lucid Lynx. Since I like to have a native client installation as well as a portable sandbox server, I decided to install the latest version of Oracle EE, 184.108.40.206. Rather than re-invent the wheel, I’m going to direct you to the previous Oracle-on-Ubuntu post by my colleague Augusto Bott. Many of the directions there hold true here (even with 32-bit vs 64-bit), with a few exceptions.
The Pythian Group Inc., the leading provider of remote database infrastructure services, announced that it is teaming with Oracle® to provide Independent Software Vendors (ISVs) with a convenient and flexible all-in-one solution for licensing Oracle products and Pythian services required to correctly plan, deploy and manage the ISV’s database infrastructure.
If you have ever had this message: Unable to locate an oracle.mk, proc.mk or other suitable *.mk file in your Oracle installation. (I looked in…) It can be a very frustrating one to track down. There is no 100% answer for this problem but there seems to be two main scenarios where I have encountered this and have come up with somewhat of a solution, here it is.
I cloned Oracle software before and it is a simple process: tar $ORACLE_HOME, copy the tar file to the new server, untar, run the cloning script which will register the new home with the inventory, and you are done! In theory, at least. Here is what actually happened:
I saw that PSU 9343627 was released and gave it a whirl. I was a little confused when the README seemed to contain a lot of instructions that always assumed it to be on a clustered, RAC install. My setup was a single-instance Grid Infrastructure installation just to provide ASM. I soon met problem upon problem when going through first this setup step. I decided to try the PSU anyway, thinking Oracle would certainly have noted in the README if this was a problem for single-node installations. Turns out I was wrong.
The process for applying a patch on top of the CRS, or now called, the Grid Infrastructure, has changed from what we used to do on 11gR1 and prior releases. The patch I had recently applied was in order to resolve the Oracle bug “220.127.116.11 ONS CORE DUMP or High Resource Usage [ID 988795.1]“. Due to the fact that the patch doesn’t require full downtime and could be applied on a rolling basis, the plan below is to be executed on each node at time.
One of the most critical skills of any Oracle DBA is the ability to prevent a system crash and to restore and recover the system in case of a disaster. The “Oracle RMAN 11g Backup and Recovery” book by Robert G. Freeman and Matthew Hart is a resource that can definitely help to acquire the skill. I recently received my early copy of it, and am honored to have contributed to Chapter 5 “Oracle Secure Backup” for it.