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.
Oracle CRS 10.2.0.3 patchset changed the logging of missed heartbeats by CSS. Here is example how heartbeats misses are logged in ocssd.log in 10.2.0.3:
Doug Burns has spent 4 weeks in our Ottawa office and now he is back home to Madeline and boys. Yesterday, before he left, we had the lunch at Cock & Lion Ale House:
Over-the-Top Tales from the Trenches: Bringing order to the chaos of every day DBA life. Ever heard this during a recovery of a downed database? The poor thing has either a minor scratch, requires immediate attention, or is dead on arrival (DOA).
Welcome to the thirtieth edition of Log Buffer, the weekly review of database blogs.
Over-the-Top Tales from the Trenches: Bringing order to the chaos of every day DBA life. My aim in any posting is to make your job as a DBA in Oracle, SQLserver and MySQL easier. Ever wondered how to get a quick count of the number of connections per hostname from MySQL? Welcome to the arcane (but extremely powerful) world of the MySQL command line pager.
One of our clients found a bug with dbms_scheduler: it logs a job as successful when a ORA-01403 is thrown. Oracle was pointing us to unpublished bug #4552696 . They said a patch is available for 11 and offered to backport the patch.
I got a call from a developer who had a table with a primary key populated by a sequence, a timestamp column with the current date and some other columns. He had a specific set of data that, when ordered by the primary key had out of order timestamps. He was puzzled how this could be. We changed the sequence to “ordered” and increased the cache to 1000. Now selecting on either node gets the next number as he expected. I warned him that there would be some performance implications due to cluster synchronization. Him being a responsive developer, asked me what the impact would be, so I tested it out.