After completing your Oracle VM and Oracle VM Manager installation, you are ready to start your friendship with Oracle VM technology. However, to make your life and experience even more enjoyable, I suggest you follow a few simple steps listed here.
This is just a quick post to share my first 3.1.1 Oracle VM Manager (OVMM) troubleshooting experience. After the initial installation, I rebooted the server, tried to access OVMM https://ovmmhost:7002/ovm/console and received the following error in a browser screen…
This blog post will be short since installing the Oracle VM Manager 3.1.1 under Dom0 host isn’t different from installing the previous version. For all the tricks you need to use, please see my Oracle VM Manager 3.0.3 under Dom0 post.
I’ve recently done two Exadata upgrades to 22.214.171.124 and want to share the experience. I hope this short note will help someone to make the decision, calculate an estimation, and prepare for maintenance. I am going to talk about upgrade from the version 126.96.36.199 BP10 to 188.8.131.52 BP2.
I had the chance to talk to several Oracle Database Appliance users at the annual Collaborate 2012 conference last month in Las Vegas. A common theme in these discussions, as well as discussions with Pythian clients, is an interest in using the ODA as a large-scale consolidation platform. I found this interesting and decided to dig a little further.
I think the results we got so far may surprise you. At lease they don’t seem to be the results +Alex Gorbachev and +Kevin Closson expected to see. You can find the first related blog post here. It will give you the necessary context for further reading. Just to recap: +Kevin Closson says that “Orion may give It’s VERY easy to get huge Orion nums but reasonable SLOB” and +Alex Gorbachev says that “lots of the system IO bound below the CPU level so you should see similar number with Orion or SLOB”. Let’s see what the first results revealed.
This is a copy of my G+ post from yesterday. As I am going to continue writing about our ongoing IO testing efforts on this blog, I decided to provide the first post here to give readers a bit more context.
They say that “April showers bring May flowers”. Basically, nature brings different things in different colors aimed at improvement. That is also true for the blogging world. This Log Buffer Edition brings out different blog posts to improve the Oracle, SQL Server, and MySQL worlds, so enjoy!
When preparing for the the IOUG Collaborate 12’s deep dive on deploying Oracle Databases for High Availability, I wanted to provide some feedback on which hardware components are failing most and least frequently. I believe I have a reasonably good idea of the answer, but I thought that providing some more objective data would be better. I couldn’t find results from a more scientific research, so I decided to organize a poll. This blog post shows the results, which I promised to share with several groups.
While doing my high availability deep dive at Collaborate 12 few weeks ago, I stated that storage replication qualifies for the cold failover licensing rules (see slide #128). During collaborate, I spoke to one person at Oracle who definitely knows the rules. Simon Haslam also reached out to me by email pointing out that things might not be that rosy. I will update the slides accordingly. In any case, please do your own homework and don’t trust my conclusions here — don’t take this as licensing advice by any means.