The 56th edition of Log Buffer, the weekly compendium of database blogs, has been published on Hasan Tongu Yilmaz’s Oracle Blog.
Yes, I know, this subject of detailed extent map of the datafiles is a rather old one, and a few different solutions have been provided by several professionals, including the famous Tom Kyte. But none of the answers I found did exactly what I wanted, and therefore, I chose to write my own solution. OEM does provide this, but for a price — the Tablespace Map is part of the Oracle Tuning Pack — and I like the free stuff and the extra flexibility I have using queries.
come from a MySQL background, and I have been given the challenge of learning Oracle. So I decided to install my own Oracle database, which I’ll be free to destroy in every way I can think of… and of course, free to bring it back to life. Recovering from crashes will probably be the most difficult part of my adventures in the Oracle world, but let’s take one step at a time, shall we? This tutorial was based on a document which can be found here. I have adapted it for Oracle 11g.
The 55th edition of Log Buffer, the weekly review of database blogs, is published on the Ardent Performance Computing Blog, thanks to Jeremy Schneider.
The 54th edition of Log Buffer, the weekly review of database blogs, has been published by Paul Gallagher on Tardate 10.2.
Last Friday, a customer paged me to say that they could not open an Oracle 8.0.5 database after the RAID array crashed. It turned out that this database was in NOARCHIVELOG mode and there was not even a cold backup. Furthermore, they didn’t even have a database export. it was definitely the time to recall Kurt Van Meerbeeck and his all-time-hit tool — the DUDE. DUDE stands for Database Unloading by Data Extraction. The client was very impressed by how we were able to recover from a deadly situation like that, and it was only possible thanks to the DUDE and his creator: thanks a lot Kurt.
Like an invincible psycho with a knife, Log Buffer is back, with a Friday the 13th issue (“Larry’s Revenge!”). Daniel Fink of OptimalDBA is the lucky one to do this 53rd edition of the weekly review of database blogs.
Let’s focus on what 11g is all about. The main message I got is that Oracle 11g is the consumer release. According to Mr. Phillips, what this means is that Oracle has listened to its clients and has worked in the areas that the consumers needed the most. The fact that Ari Kaplan, the president of the IOUG, was on stage during the launch speaks for itself. As for what’s new in 11g, three major features come to mind…
n the following SQL*Plus output something is goofed up. You should not have a no rows selected with this SQL. When you see something like that for the first time, you can generally draw from four conclusions: Someone edited the output, SQL*Plus bug, Oracle bug, combination of the above. Since it was me who saw this, number one was an easy but irrelevant answer. What about an SQL*Plus bug? OK, run this using some other ad hoc tool. Same result. Time to take a more precise look at the problem. What is trans?
Taking the cue from Jay Pipes, as so many other bloggers have done, I present the five things I would most like to see in a future release of MySQL.