Two new features that really caught my eye were :the ability to apply application upgrades while the database is up and the connection pooling IN the database.
The client entrusted me with the migration of one of their mission critical apps running 8i on HPUX to — drum role please — 9i … on … IBM Mainframe running os390 (z/os). For this client, we were able to shave $600,000 (not just the Oracle license, but also the external costs of maintaining the environment) by migrating just one HPUX machine over to the mainframe with maybe 30 or more to go.
UKOUG 2006- I have three sessions there. These are first three right on Tuesday after the Opening Technical Keynote by Tom Kyte.
Over the last weekend I had the pleasure to do an 8i -> 10g, Solaris -> Linux migration. Talk about going in head–first. Now, whenever I run into a situation like this, we generally recommend a two–step process so that we can iron out bugs and be able to isolate causes. However, we were under serious time constraints, and we decided to just go with the following simple plan and move straight there.
Welcome to the 18th Log Buffer, the weekly human-edited review of news from database blogs.
While reviewing some material in advance of my presentation at UKOUG Conference 2006, I found an interesting change in RMAN behavior in Oracle 10g. The difference is in the way RMAN handles the case when an incremental level 1 backup is taken without an available level 0 backup. This probably won’t affect anyone much, but I found it interesting. And actually, there are scenarios in which it might cause issues.
I have been working on issues that relate to security certification at a number of our clients, and I can’t say that I have anything good to say about it.. Compliance standards are set such that you are protecting against the bulk of the people out there. This is generally very good practice, but when you rely on standardization alone, you open yourself to real danger.
The latest release of DBD::Oracle is now ready and can be found at CPAN DBD::Oracle
Recently we’ve had quite a few migrations to 10g Release 2 and several times been hit by one issue some users consistently get locked with status LOCKED(TIMED). One good example is with the DBSNMP and SYSMAN users, but more important are locked production accounts.
In the last month, we have been hit with two clients’ large-scale failures. The first involved network issues; the second, disk failures. What happened?. We took one of the standbys and turned it into a primary. The other standby then automatically started recovering from the new primary! That was it. What a let down! No magical status updates, no little “dots” going across the screen. Just one line and 15 seconds. Oracle, get your act together! I even had to use bold text to make it stand out.