Posts Categorized: Technical Blog
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…
It happens to be very short blog post as installation the Oracle VM Manager 3.1.1 under Dom0 host isn’t different from installing the previous version. For all tricks that you need to use please see my Oracle VM Manager 3.0.3 under Dom0 post.
I’ve recently upgrade couple of exadata to 126.96.36.199 and want to share the experience. I hope this short note will help someone to make the decision, calculate estimation and prepare for maintenance. I am going to talk about upgrade from the version 188.8.131.52 BP10 to 184.108.40.206 BP2.
I had a chance to talk to several Oracle Database Appliance users at the annual Collaborate 2012 conference last month in Las Vegas. And a common theme in this 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 those doesn’t seems to be the results +Alex Gorbachev and +Kevin Closson expected to see. You can find the first related blog post over here. It will give you the necessary context for further reading. Just to recap: +Kevin Closson says “Orion may give It’s VERY easy to get huge Orion nums but reasonable SLOB” and +Alex Gorbachev “lots of the system IO bound below the CPU level so you should see similar number with Orion or SLOB.” Let see what first testing results revealed.
I am going to continue writing about our ongoing IO testing efforts under this blog I decided to provide the first post here to give readers a bit more context. SLOB is nothing but a ~84MB schema with a table and index created in Oracle database to test LIO (if you set a big db_cache_size) or PIO (if you sent a small db_cache). Well by default there are 128 schemas created with the same data structures.IMHO: This is a very good idea to test the performance by executing the same actions that most of Applications do in a real live, but make it so simple that it is application agnostic.
My work was related to Tablespace management in 5.6 and Table partition EXCHANGE, you can read the articles here. I have also start to dig a little bit more in details on Mongo architecture, given the need to have it correctly review and implemented in parallel with MySQL installations. As news review I was more interested in a couple of articles, as for below
When preparing for the the IOUG Collaborate 12 deep dive on deploying Oracle Databases for high Availability, I wanted to provide some feedback on what hardware components are failing most frequently and which ones are less frequently. I believe I have reasonably good idea about that but I thought that providing some more objective data would be better. I couldn’t find and results of a more scientific research so I decided to organize a poll. This blog post shows the results and I promised to share it 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 you own homework and don’t trust my conclusions here — don’t take this as a licensing advice by any means.
Our flagship tool, Support Track, is steadily migrating over to use DBIx::Class to read and manipulate our databases. This is a very useful tool, for many reasons which many people explain better than I could. One of those reasons is that — thanks to the magic of SQLite — it lets us write unit test scripts, and other quick prototyping code, without needing to set up a heavy database server to run against. However, Support Track is powered by Oracle, not SQLite, and while DBIx::Class abstracts most of the differences out of our code, it can’t completely eliminate them. How do we overcome the syntactic differences?