Those of you who, like we do here at Pythian, have the pleasure of supporting both MySQL and Oracle environments (among others) will definitely know who Tom Kyte is. In any event, reading his blog today I noticed that over the weekend he posted on an error message blurted out of a wordpress environment… something about how the “[MySQL server has gone away]“
In a story that we’ve been following a long, long time, Oracle finally succumbed to multi-core pricing pressure today.
So you have swallowed the standby bait. You have used RMAN duplicate to create a sparkling new standby and things are looking rosy. Then, when you check the lag between the primary and standby (in MAXIMUM PERFORMANCE mode), you discover the standby is miles behind. Oracle (at least from 9iG) rides to the rescue again. The parameter ARCHIVE_LAG_TARGET tells Oracle to make sure to switch a log every n seconds.
In this new installment of Pythian Goodies Doug Burns discusses Parallel Basics. This video is a good introduction to using Oracle Parallel features and most importantly, what problems you may have with it.
As usual, Oracle introduces new features, and we read the documentation about how they work and we start using them… but what about what is not in the documentation? That we find out by practice, experience, or accident. And that is exactly what happened to me today.
Last week, we discovered a bug related to the rollback of the Java DST patch for 9206 on Linux x86. If you’re in the unfortunate position of needing to roll this patch back, you won’t be able to. When you rollback, you need to restore both of these files, and then do a create or replace java system. Otherwise you risk hitting a dreaded ORA-03114 End of file on communication channel. Those of you familiar with DST patching will have seen this, but for those who haven’t, here are the scripts you need to check for a successful Java implementation:
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!
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.
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.