Introduction

“Practical C Programming” not only plans to teach you C, but also about style, debugging and the software life-cycle.

Introduction

Those two point, on their own, were enough to clinch the purchase just over eighteen months ago.

Content

The book is, to say the least, comprehensive. When I first started to use PL/SQL I would never have guessed that there was enough there to write a thousand page book, but there is.

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 Data Browser

Oracle Data Browser, part of the Discover 2000 suite, is one of the least amusing applications that Oracle supply. Not because it’s bad, but because it almost works…

• Windows 95 has a ‘full screen drag’ feature (freely download-able from Microsoft‘s web site). If you load Data Browser you don’t. It suddenly stops working.
• Now this is supposed to be a feature, but I’m not convinced. The word ‘Browser’ seems to indicate that it’s a read-only product. In fact a version comes with it that isn’t.

Oracle Data Query

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.

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.

This is neither a new book nor a new purchase for me, so why am I reviewing it? Bottom line: it’s a book that I’ve enjoyed a lot over the years and one that I feel the need to recommend to as many people as possible.

What’s in it?

The obvious format for a book on the personal computer industry would be chronological, but as he points out early on in the book, things just aren’t that simple. Instead he uses what, on paper, might look to be a random arrangment of anecdotes, jumping from Apple to Xerox Parc to Microsoft and IBM in the matter of a few pages. But that’s just the nature of the beast.

Eric Raymond would have us believe that everyone that develops software for fun is a hacker. I know that historically this has always been the case, but that doesn’t necessarily make it the right thing. All good, and bad, things come to an end.

I doubt that it will happen any time soon, but I think that ‘hacker’ is a term that should whither and die.

The first problem, and this is the obvious one, is the public perception of it. Yes we all know that hackers write code while crackers break into computer systems, but how many people ‘outside’ know that? How many professional software developers, i.e., those who do it just for a living rather than for fun, know that?