Posts Categorized: Technical Blog
Many readers of these BLOG posts are seasoned attendees/presenters at this IOUG/OAUG/Quest collaborative event held every spring. User group events are the one of the best stomping ground for hungry IT specialists, thirsting for news on late-breaking solutions and more traditional technologies.
In my previous post I described how to install Oracle VM and Oracle VM Manager on the same sandbox. However, to start playing with Oracle VM v3 you need to configure some storage to be used for new VM hosts. The problem is that Oracle states that you should allocate a full HDD for VM host storage. If you have just one HDD in your system then you are in trouble, as part of it is already occupied by the Dom0 host.
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’s 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 with Amazon’s default Xen hypervisor. Here are the steps I used…
Just a quick heads up to the ODA customers — there is a critical patch 188.8.131.52.1 out that is applied on top of ODA patch bundle 184.108.40.206.0. This patch has an important fix for a bug causing ODA servers to shutdown in some situations when an ASM disk is lost.
The method of disabling triggers requires Oracle 220.127.116.11+ 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:
The biggest objection to Oracle Database Appliance (ODA) we hear from customers is about 4TB usable space limit (tripple mirrored 12TB of raw storage). I think most of the times this is more a perceived barrier rather than objective — more along the lines of being afraid to hit the limit if the system grows a lot. Nevertheless, Oracle has been always listening customers’ concerns when it comes to purchasing barriers. Of course, this time is no exception.
Stumbled upon this Dell’s article from 2001, So what do we see 10 years later? Singe device, no fuss, everything pre-configured, Oracle RAC, simplified operations — dream of 2001 finally coming true?
Hello Friends, This is a short blog post to let you know that I am going to give my RMAN and SCAN talks to WA OUG (AUSOUG) folks in Perth next week. Here are the details:
The forwarded case didn’t have many details. Its a 9i system that started experiencing ORA-4031 errors sporadically over the last few weeks. Marc suggested using R to explore how the various SGA components changed sizes over the last few weeks and see whether we can find any interesting trends that can indicate memory leaks. So we did just that. The first step is to get the actual data out of the system, and we used the following query