I spent Friday morning installing -- er, trying to install -- Oracle database ODBC drivers so that some College staff could connect to our shiny new server using Microsoft Access. It took until lunchtime to get two computers configured, including the time to write out a four-page instruction manual for the process.
Installing drivers on staff computers is not the sort of thing I usually do, but we were in the midst of a considerable system upgrade, and that was one of the ways I could be helpful.
Normally, installing an ODBC driver is a matter of running a small installation program -- assuming Windows doesn't already come bundled with the driver -- and entering some server specifics for something called a DSN. Five minutes, tops.
Not so for Oracle. The procedure I eventually scratched together required manually "deinstalling" (Oracle's terminology) every pre-existing scrap of Oracle gunk and then "undeinstalling" (my terminology) the full-blown administrator client, consisting of the aforementioned ODBC driver along with about 400MB of ugly, ugly Java programs. Depending upon the age of the computer (a predictor of the amount of Oracle cruft that had accumulated), the entire process ate up between 15 and 45 minutes per.
I'm sure there is an easier way. Oracle's site certainly seemed to suggest so, offering sundry downloadable utilities to non-Cubans, non-Iranians, and non-North Koreans, but even the Googlesphere was silent on how to actually employ these downloads to solve an earthly problem.
As a one-time/short-time/part-time Oracle DBA, I'm not wholly unfamiliar with the nefarious machinations of Oracle configuration. I used to consider it a week well spent if I could log in to a newly-installed database through a network.
But that was years ago, before competition from Microsoft and Open Source started wheedling away at Oracle's dominance (warning: possible ass-yanked statistics). Why haven't the tools improved in the interim? Why are the user interfaces so hideously grotesque? Why does every aspect of Oracle configuration have to be so spirit-crushingly complex?
My best guess is that the company doesn't want to cannibalize the third-party support industry that has grown up around it. So they produce the lamest-but-legally-functioning tools possible, leaving it to their partners to sell multi-kilobuck slightly-less-lame products.
I should distribute that four-page installation manual from Friday to CIOs from around the country. Let the ones about to shell out fifty-grand-plus for an Oracle license set up an ODBC connection during lunch. I'd make 'em do it twice, but there may not be time.
- A Real DBA on 20070608.Friday:
I'm sorry to say this, but if you had a hard time installing an Oracle client and the ODBC drivers from the latest version of Oracle, then you are indeed technically challenged. I've been working with Oracle since version 7.3, and while I do agree that Oracle heaps on the Java, I have to say that the Oracle client and the ODBC drivers are a snap to install, and you can do it without loading up all 400mb of Java garbage. I've done it on slow machines in less than 15 or 20 minutes. On newer machines, it's even faster than that (as in less than 10). Oracle is not all that complex, if you know what you are doing. If you don't know the technology stack, then you will hit the wall. It's as plain and simple as that.
- Dave on 20070608.Friday:
If I was setting up Parallel Server or replication, then your point is well taken. But an ODBC driver? That it takes a "Real DBA" as long as 20 minutes is not a flattering portrayal of Mr. Ellison's database.