Posts Categorized: Pythian
A new trial version of DBD::Oracle is on CPAN. The meat of this release is the awesome work Martin Evans did in the murky core of the beast. He explains it better, but basically his magic results is a much faster DBD::Oracle on thread-enabled perls. This being said, the changes he did are significant (2.3K lines changed according to Git), and we would be very grateful for anybody finding the time to try and install that trial version before it goes live (which, unless something wrong is found, should be in 2 weeks).
The weather is changing, clocks are being adjusted, and the changes at the technological front are as usual rapid, frequent, and over-whelming. Keeping up with such rapid-fire changes is a project in itself. In the database triangle of Oracle, SQL Server, and MySQL, patches, updates, features, tricks, and tips are booming, and so is this Log Buffer Edition.
Many readers of these BLOG posts are seasoned attendees/presenters at this IOUG/OAUG/Quest collaborative event held every spring. User group events are 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 since part of it is already occupied by the Dom0 host.
By now, I have a few Dist::Zilla plugins interacting with the distribution’s changelog. Each time I get the changelog, I parse it into a CPAN::Changes object, do something to it, and save it again. It’s actually not even as hard as it sounds. Have a look.
Just a quick heads up to the ODA customers — there is a critical patch 126.96.36.199.1 out that is applied on top of ODA patch bundle 188.8.131.52.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 184.108.40.206+ 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?
Today I got an email reminder that the Metacpan logos are all in and that the voting booths are open, and will be so until Friday the 30th of March 2012, 23:00:00 UTC.