Welcome to the 33rd edition of Log Buffer, the weekly review of database blogs. We’ll look at some of the standout blog items from the week gone by.
Sorry if everyone else already knows this, but I just got some Oracle spam inviting me to EM 10GR3 launch party, and it’s scheduled as a “live online launch” on March 13, at 9:30. So those of you who are waiting with bated breath for the DST projects to be over now have something else to look forward to a couple days later!
Unfortunately, I’m too slow to blog about news and can never make it first. Today is no exception and Doug Burns has already posted about “one of the best Oracle Conferences of all times”: I can tell you – I’m so excited to see all those bright people presenting. It’s especially a pleasure to see that Doug (who recently joined my team here at Pythian) is presenting there.
The 32nd edition of Log Buffer, the weekly review of database blogs, has been published by Lewis Cunningham on An Expert’s Guide to Oracle Technology.
Two weeks ago, I released a video about Flash Recovery Area as part of the Pythian Goodies project. Here is the next video in the sequence, Oracle I/O Basics.
Oracle CRS 10.2.0.3 patchset brings long awaited removal of previously required dependencies of databases and ASM instances on a VIP. Actually, 10.2.0.2 patchset lifted the requirement for dependency between ASM instance and VIP but not for database instances. In 10.2.0.2 this dependency wasn’t removed by default. For those who don’t know…
Just a small thought to share. Oracle doesn’t really comply to the rule 11 of Codd’s 12 rules. It does have database links and tables can be grouped in different locations (databases) but it’s not possible to distribute a table transparently across several locations. MySQL Cluster, on the other hand, distributes rows of a table over different data nodes using hash function on the primary key and it’s transparent to the client so it conforms to the Rule 11 as opposed to Oracle.
Welcome, to the 31st edition of Log Buffer, the weekly survey of database blogs.
Here’s the challenge. How do I post to both work and personal blogs and provide appropriate material for both? It’s not a problem I expected to face because most employers, at least where I’m from, wouldn’t entertain the idea of employees blogging on company time to the company blog, far less encourage it. Which is one of several reasons that I found myself choosing to work with Pythian.
This is a follow up on my previous post about SYSDBA keeping invoker rights when calling PL/SQL procedure. Working on the previous test case a bit more I figured that the same anomaly is observed with triggers. So here is one way to get your PL/SQL code called by a SYSDBA. In this case you need to be able to create trigger on database, i. e. need privileges ADMINISTER DATABASE TRIGGER and CREATE TRIGGER.