Welcome to the Oracle Comedy Errors Page!
This page is dedicated to all those frustrating hours that you have to spend fiddling about with Oracle just to get it working as it says it does on the box.
These are just things that have happened to me and the projects that I have been involved in. To make a really complete Oracle Comedy Errors Page we need your input.
For those that have already contributed, there is always this page. It also catalogues the projects and Oracle software that I’ve used to build up this list.
Why is this page here?
There seems to be a great number of people who are only too eager to bash Microsoft, but only a few who seem to hate Oracle. Looking at their products, I thought that there must be at least a few sympathetic souls on the net. A quick search on HotBot and Altavista seems to indicate otherwise.
To rectify this shameless situation, I aim to produce, if not the first, then the definitive list of Oracle cock-ups and anecdotes. Naturally, I can’t do this all on my own; there are others.
I can supply the TAR numbers if you don’t believe me…
Working eight hours a day with a product, you notice not only bugs, but other strange bits and pieces too. This is the page for them.
- One mis-spelling of ‘Oracle’ looks remarkably like ‘Roach.’ Surely not just a coincidence.
- Mis-typing ‘ORACLE_SID’ often looks like ‘ORACLE_SOD’ which is only one word short of what you usually think when you’ve done this.
Fair’s fair, any application the size and complexity of Oracle Applications will have some bugs. But applications seems to do far better than most.
This section refers to the server size of Applications Comedy Errors. There’s another page for the client side.
- To install a new application module, it seems that you have to add the original version you have plus all patches. Not just for your new module, but for all of them. (People that implement Application’s are not expected to make mistakes.)
- The recommended sizes for your database extents are useful. However, if you follow the advice, some parts of the system won’t actually install.
- Oracle helpfully supply a program that goes through the thousands of files that it installs and checks that they’re the right ones. We’ve found at least a dozen files that it claims shouldn’t be there but in fact should be.
- After applying a patch, the shell script that starts the Concurrent Managers just vanished.
- One of the bugs that we found was because Oracle had ‘forgotten’ to port a number of forms from one environment to the one we were using. The word ‘forgotten,’ despite being inverted commas, is the actual word used by Oracle support.
Oracle, the company, was founded back in the late seventies as a company that produced an SQL database. Its entire reputation has been built on this product and it is, therefore, no surprise that it is very good.
That’s not to say that there have been no problems…
- To perform dodgy ‘system’ operations on a database, you need access to a user called ‘internal.’ In theory, you need to be in the UNIX ‘dba’ group to be able to connect. That is unless you belong to rather a lot of groups, in which case it doesn’t seem to work. (We’ve not actually called this through, so there may be a simple explanation.) (7.1)
- When creating a new database, you have to run a file called ‘catalog.sql’ to finish the job. At the end of this file is the following message: ‘THIS IS THE END OF THIS FILE – IF I AM NOT HERE THEN RCS HAS TRUNCATED FILE‘ (7.3)
- I’m not entirely sure that this counts, but an installation program that requires more resources than that product that it’s installing demands at least an honorable mention. (8i)
Don’t get me wrong. Oracle support analysts have a difficult job. Their products are large, complex beasts and you don’t necessarily expect an immediate response. These, however, I did not expect…
- Having spent over a day with hourly contact with support, they ring back returning a voice-mail message left before managing speaking to a ‘real’ person. Twenty-seven hours apparently wasn’t enough for a correct response, either.
- Two weeks of problems lead to a call to our sales manager. Obviously concerned, he went away to research the problem. He came back a day or two later. “This problem you’re having with you SCSI CD-ROM…,” he began. Good effort, wrong customer.
- They asked us to download a patch from their web site, a mere 36Megs. This looked remarkably similar to a patch we’d received the previous week for another problem. Next they insisted that we needed the next version of the SmartClient software. They even sent someone out to install it for us. Naturally, this solution didn’t work. They ummed and arred for a while before declaring it a ‘bug’ and sending it off to the states to be fixed. This is the last I heard of this problem.
Credit where it’s due
I am unable to criticise a suite of products the size and complexity of Oracle on my own. There are a number of people that need to me mentioned. Remind me if I missed you out!
Thanks to Anna Brabants who nearly created the term ‘Oracle Comedy Errors’ and certainly did an almost continuous stream of abuse (not all of it at Oracle).
And thanks to the rest of the project team, who invariable love Oracle products as much as I do.
Thanks to the people at Oracle support who no doubt have to put up with a lot, and offer much amusement if only after the event.
I’ve been on a number of projects that use Oracle, however most of the tales have come from the first two. On these I was a DBA and developer and ended up spending much time on the phone to Oracle support.
The first time, we were implementing Oracle Financials and Human Resources using a Sun UltraEnterprise 1 server and Compaq workstations.
The server was running Solaris 2.5, with Oracle Server 7.1.6, Oracle Applications 10.6.1 and an incredibly large number of patches.
The Compaq P166 clients ran Windows 95, with SmartClient Prod 15. Then Prod 15.1. And then with a number of ineffective patches… You get the idea.
The second time, we were implementing a bespoke client-server application. The Sun Ultra 1 (and later Ultra 2) server was running Solaris 2.5.1 (2.6) with Oracle Workgroup Server 7.3.
The Compaq P133 clients ran Windows NT 4 and connected to Oracle using OLE Objects through Microsoft Visual Basic 5.
Since then I’ve worked mainly as a developer (often doing data-loads) on Oracle 8. Any 8i critiques come from developing my 8i on Linux HOWTO.