The method of disabling triggers requires Oracle 188.8.131.52+ 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.
There is so much to learn out there. So much to accomplish and so much to devour technically. It can be daunting and overwhelming to have so much in one’s plate, and that is why this Log Buffer Edition has culled some top notch blog posts for you in Log buffer #264.
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
TEMPDB, is one of SQL server hot-debated topics; there’s always something to say about its sizing, file placement or datafiles count in Multi-core instances. This is simply because TEMPDB is a global resource that’s heavily used and very critical asset in a busy instance; this makes any advice against TEMPDB fall in the “It depends” category.
The pièce de résistance is Dist::Zilla::Plugin::NextVersion::Semantic which I had promised to Mike Doherty a long time ago. In a nutshell, the plugin examines the changes of the upcoming release and increases the version according to the rules of semantic versioning.
In this Log Buffer Edition, March madness with method continues with plethora of blog posts from across different database technologies. Enjoy this Log Buffer #263.