Posts by Marc Fielding
Update 13-June-2012: It has come to my attention that the numbers from the original source may have been incorrect or improperly released. To avoid confusion and potentially misleading information, the original content of this blog post has been removed.
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.
If you’re planning on running Oracle VM with Amazon EC2, there are some important limitations you should know about. As part of my work getting the Oracle Linux Unbreakable Enterprise Kernel 2 working, I tried using the Oracle-supplied Oracle Linux 6 AMI images that are listed as community AMIs by Amazon. Here are my findings.
I’m going to test Oracle’s Unbreakable Enterprise Kernel out, and an obvious way to do this would be using Amazon EC2, providing high-capacity instances on demand. After some blind allies getting the Oracle Linux UEK2 kernel working with Amazon EC2 and Oracle VM, I found that I could make it work without Oracle VM, with Amazon’s default Xen hypervisor. Here are the steps I used.
The method of disabling triggers requires Oracle 22.214.171.124+ or 10.2.0.5+, plus execute permissions on sys.dbms_xstream_gg. Since it’s a call to an XStream package, it may also require a XStream license. So if I haven’t scared you away yet, here’s a quick testcase:
Those of you who have seen me present about GoldenGate will know that I recommend using a heartbeat table to monitor GoldenGate lag. The heartbeat table is a great way to monitor GoldenGate replication because it can follow a single SQL insert through each major GoldenGate replication process, and report the replication lag attributable to each.
I was browsing My Oracle Support today, and came across note Note 1415713.1 which talks about updates to third-party monitoring agent support. According to the note and associated FAQ, as of February 15, 2012, all third-party monitoring agents are supported on the Oracle Database Appliance (ODA). This means that the previously-published list of supported third-party agents on OTN no longer applies. The biggest benefit to the policy change will be for people who use in-house or open-source monitoring tools like Nagios or newer replacements.
The end is nigh for Adobe Flash at My Oracle Support. The first step will happen during this weekend’s planned maintenance of My Oracle support, when all of MOS will be down for 5 hours starting at midnight eastern, Saturday January 28. Once it comes back up, the unadvertised non-Flash supporthtml.oracle.com will come up as a quasi-user acceptance test of the new application, while the flash-based support.oracle.com stays as-is.
The 2012 edition of RMOUG Training Days in Denver less than a month away, running February 15 and 16 at the Colorado Convention Center in Denver. . It’s not too late to register, and it’s a pretty nice excuse to get to the Rockies in ski season. I’ll be doing two presentations, and am polishing up whitepapers and presentations for the submission deadline tomorrow
Hot on the heels of 126.96.36.199 coming out for Exadata, there’s yet another Exadata patch schedule out: the Quarterly Database Patch for Exadata (QDPE). They’re designed to being some of the predictability of Oracle’s quarterly critical patch updates (CPU) to the Exadata world.