Tag Archives: database

Installing Oracle on Redhat 8

In all honesty, I’ve not managed to get Oracle working properly yet. When I upgraded my RedHat 7 machine to 8 it still worked, when I installed it from scratch it didn’t. This clearly shows that it’s possible to get Oracle 8i working, but I can’t say how!

For those that are interested, I found that it was easy to get the installer to complete, but I get the infamous “end of communication channel” error when trying to start an instance.

About Oracle Comedy Errors

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!

People

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.

Sources

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.

Oracle Comedy Errors Home

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…

Content

Installing Oracle on Redhat 7

Introduction

The subject at hand is really much wider than just Redhat 7.x, especially as more recent distributions are following Redhats lead and are now including glibc 2.2 also. I have no reason to believe that this process will not work with newer versions of SuSE, Debian, etc.

The other point to note is that I have not tried the procedure outlined here. I have migrated my box from Debian 2.2 to RedHat 7.2 and can testify that Oracle still works, but I have not actually performed an installation. I have, however, recieved a good number of emails confirming that it works, so don’t worry!

Most of the following material comes from two people, who are the real people you should thank if it works for you. They are John Smiley and Max McClanahan.

The process

The problem is that Oracle 8.1.x needs glibc 2.1.3. It will link without error with glibc 2.2, but when you try to run dbassist or create a database from scratch, there are problems (dbassist hangs, ‘End of file on communication channel’, etc.)

Here is a step-by-step process for getting Oracle 8.1.6 or 8.1.7 working on systems with glibc 2.2 (don’t bother with 8.1.5 if you can help it). Note that 9i requires glibc 2.2 and will not work with earlier versions:

  1. Install the compat-glibc RPM for 2.1.3. The exact filename will vary depending on your version of RedHat or other distribution. Many people (Fernando Boaglio, Peter Whysall, Jose T. Martin Prior amongst others) have noted that Oracle provide a patch (glibc-2.1.3-stubs.tar.gz) that provides the same functionality. I prefer the RPM’s personally, but this will certainly work.
  2. Execute the following command: . /usr/i386-glib21-linux/bin/i386-glibc21-linux-env.sh
  3. Type “export LD_ASSUME_KERNEL=2.2.5”
  4. Type: cd $ORACLE_HOME/bin
  5. Run the following command from the UNIX prompt: relink all

All of the Oracle software, including the assitants, will work fine now.

This technique will work on RedHat 7.0 with the 2.2.16 kernel, as well as the 2.4.0 and 2.4.1-pre11 kernels.

The rest

John Smiley also asked me to point out that Oracle have issues some patches (ftp://205.227.44.220/server/patchsets/unix/LINUX/8161/bug1467074/) that are required in order for them to consider your machine ‘certified’:

Operating System: Intel Based Server LINUX Version:Red Hat 7.0
Oracle Server - Enterprise Edition Version: 8.1.7 (8i)
N/A Version: N/A
Status: Certified
Oracle Server - Enterprise Edition Version: 8.1.7 (8i)
Bug Number: 1467074
REDHAT 7.0/ORA-3113 ISSUE (GLIBC 2.1.94 AND LATER)
Patch for bug 1467074 is mandatory for this certification.

RedHat even have a bug report on this issue, which may be worth a look: Bugzilla report from Redhat.

Oracle Server Comedy Errors

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)