Installing Oracle9i on RedHat Linux 7.2, 7.3, 8.0, 9, AS 2.1, 3.0 (Red Hat Enterprise Advanced Server 3 – RHEL AS 3) (Oracle database installation, install Oracle software)

                       Werner Puschitz

      


Red Hat &REG Certified Engineer (RHCE)

       Linux Professional since 1997

          Homepage of Werner Puschitz

Installing Oracle 9i on
RedHat Linux 7.1, 7.2, 7.3, 8.0, 9, Red Hat Advanced Server 2.1, and on Red Hat Enterprise Linux Advanced Server 3 (RHEL AS 3)



>>> Werner’s Oracle – Linux Page <<<

Here is a summary (HOWTO) of how I installed:

Oracle 9iR2 (9.2.0) Database on Red Hat Advanced Server 3 (kernel 2.4.21-4.EL, glibc 2.3.2-95.3)

Oracle 9iR2 (9.2.0) Database on Red Hat Advanced Server 2.1 (kernel 2.4.9-e.3, glibc 2.2.4-26)

Oracle 9iR2 (9.2.0) Database on Red Hat 9 (kernel kernel-2.4.20-6, glibc 2.3.2-5)

Oracle 9iR2 (9.2.0) Database on Red Hat 8.0 (kernel 2.4.18-18.8.0, glibc 2.2.93-5)

Oracle 9iR2 (9.2.0) Database on Red Hat 7.3 (kernel 2.4.18-3, glibc 2.2.5-34)

Oracle 9iR1 (9.0.1) Database on Red Hat 7.3 (kernel 2.4.18-3, glibc 2.2.5-34)

Oracle 9iR1 (9.0.1) Database on Red Hat 7.2 (kernel 2.4.7-10, glibc 2.2.4-13)

Oracle 9iR1 (9.0.1) Database on Red Hat 7.1 (kernel 2.4.2-2, glibc 2.2.2-10)

People recommended this installation guide also for Red Hat Fedora Core 2.

Validation/Certification:

For Validations/Certifications, check the following links:


Oracle’s Certification Matrices


Oracle Products on Red Hat Linux


Red Hat Enterprise Linux Application List

Errors and Problems:

Some of the Oracle errors and problems covered here were only experienced in connection with 9i (9.0.1)
and some only with 9iR2 (9.2.0).
But since I cannot say for sure that a 9i (9.0.1) installation error will never show up
during 9iR2 (9.2.0) installation, I simply kept all errors and problems listed together, see

Oracle Installation Errors
and
Oracle Installation Problems, Important Tips and Hints.

Red Hat Enterprise Linux Advanced Server 3 (RHEL AS 3)

In order to install an Oracle9iR2 database on RH AS 3, the “Oracle9iR2 Patch Set 3 9.2.0.4.0”
patchset and some other patches must be applied. Some errors can only be fixed by applying
the 9.2.0.4 patchset. For more information, see

Running Oracle Installation on Red Hat Enterprise Linux Advanced Server 3.

Red Hat 9:

Red Hat 9 includes now the the Native POSIX Thread Library (NPTL) which is an improved
implementation of POSIX threads for Linux. But using NPTL will cause several problems for Oracle
applications. Note that Oracle9i has not been certified on Red Hat 9!

So to fix this problem, you can set the environment variable LD_ASSUME_KERNEL to 2.4.1,
which means that the old “Linuxthreads with floating stacks” implementation will be used. Otherwise
the Oracle installer runInstaller will hang, the Database Configuration Assistant dbca won’t start etc.; see

Oracle Installation Errors for more information.
To see where this environment variable can be set, see

Set Oracle Environments.
For more information on LD_ASSUME_KERNEL, see

Red Hat Linux 9 Release Notes.

NOTE: Before you install Oracle9iR2, make sure that you first read the information about the error message
“Error in invoking target install of make file /opt/oracle/product/9.2.0/network/lib/ins_oemagent.mk“
in the

Oracle Installation Errors section!

Red Hat 8.0:

The only problem I experienced with Oracle 9iR2 (9.2.0) on Red Hat 8.0 was:

"Error in invoking target install of makefile /opt/oracle/product/9.2.0/ctx/lib/ins_ctx.mk"

But this does not necessarily mean that you won’t see other problems described here.
See
Oracle Installation Errors for more information.

 

This article covers the following subjects and steps:

*
Documentations

*
Downloading and Installing Red Hat Linux 7.1, 7.2, 7.3, 8.0, 9

*
Unpacking Downloaded Oracle9i Installation Files and Burning Oracle9i CDs

*
Setting Swap Space

*
Setting Shared Memory

*
Checking /tmp Space

*
Sizing Oracle Disk Space

*
The “binutils” Issue

*
Checking Development Packages (RPMs)

*
JDK

*
Creating Oracle User Accounts

*
Creating Oracle Directories

*
Setting Oracle Environments

*
Starting runInstaller

*
Running Oracle Installation on RH 7.1, 7.2, 7.3, 8.0, 9, and on RH AS 2.1

*
Running Oracle Installation on Red Hat Enterprise Linux Advanced Server 3

    
Installing Oracle9iR2 on RH AS 3

    
Patching Oracle9iR2 on RH AS 3

    
Patching Oracle Intelligent Agent on RH AS 3

*
Startup and Shutdown of the Oracle 9i Database

*
Oracle Installation Problems, Tips and Hints

*
Oracle Installation Errors

Documentations


Oracle9i Database Documentation for Linux


Tuning and Optimizing Red Hat Linux Advanced Server for Oracle9i Database


Oracle9iR2 on Linux: Performance, Reliability and
Manageability Enhancements on Red Hat Linux Advanced Server 2.1


An Overview of Red Hat Advanced Server V2.1 Reliability, Availability,
Scalability, and Manageability (RASM) Features


Downloading and Installing Red Hat Linux 7.1, 7.2, 7.3, 8.0, 9

To download Red Hat Linux 7.x, 8.0, 9, check the links at
http://www.puschitz.com/RedhatDownload.html

You can find the installation guides for installing Red Hat Linux under
Red Hat Linux Manuals.

NOTE: You cannot download Red Hat Linux Advanced Server 2.1,
you can only download the source code. If you want to get the binary CDs,
you will have to buy it at

http://www.redhat.com/software/linux/advanced/.

Installing Software Packages (RPMs)

You don’t have to install all RPMs when you want to run an Oracle9i database on Red Hat Linux.

For instance, if you install Red Hat Advanced Server, you are fine when you select the
Installation Type “Advanced Server” and when you don’t select the
Package Group “Software Development”. There are only a few other RPMs that are
required for installing Oracle9i. These other RPMs are covered in this article.

Or when you install Oracle9i on Red Hat Linux 7.x, 8.0, or 9, you are fine when you select
the installation type “Server”.


Unpacking Downloaded Oracle9i Installation Files and Burning Oracle9i CDs

Download Oracle9i for Linux from the following web site:


http://otn.oracle.com/software/products/oracle9i/htdocs/linuxsoft.html

Uncompress and unpack downloaded files:

For Oracle9i (9.2.0):

One step procedure (uses less disk space and is faster):

Two step procedure:

For Oracle9i (9.0.1):

One step procedure (uses less disk space and is faster):

Two step procedure:

Now you should have 3 directories containing installation files:

I executed the following commands when I burned the 3 CDs:

(You can get the dev numbers when you execute cdrecord -scanbus).


Setting Swap Space

In order to perform a typical Oracle 9i installation and to create a simple
prototype database, Oracle says that you need a minimum of 512MB of RAM for the
Oracle9i (9.0.1) Server, and the amount of disk space (swap space) should be
equal to twice the amount of RAM or at least 400 MB, whichever is greater.

I tried to test the limits on an older PC with 256 MB of RAM and with 600 MB of
swap space. I was able to install Oracle 9i (9.0.1 & 9.2.0) and Oracle’s default
database without any problems. But
when I used less swap space on this PC (256MB RAM), I was runnig out of memory.
So I definitely recommend to use more RAM and/or more swap space as specified in
the Oracle installation guide.

NOTE: If you do not have enough swap space or RAM during the Oracle installation,
in particular during the database creation, your Oracle server (Linux) will
temporarily become unresponsive to any events for several minutes.

For more information on correctly sizing the swap space for your database, see

Sizing Swap Space.

To check the memory, run:

To check the swap space, run:

You can also add temporary swap space by creating a temporary swap file
instead of using a raw device. Here is the procedure:

To disable the temporary swap space execute the following commands:


Setting Shared Memory

For Oracle 9i (9.2.0) installation I had to increase the maximum shared
memory size on my Linux server for all Red Hat versions.
The Oracle Database Configuration Assistant displayed the following error message on my server:

I temporarely increased the shmmax setting for the kernel by executing the
following command:

It is recommended to increase the shmmax setting permanently for Oracle. For more
information, see

Setting Shared Memory.

For more information on optimizing shared memory settings for Oracle databases on Linux, see

Setting Shared Memory. These parameters apply to all Red Hat Linux versions.
But note that except for the shmmax parameter, these parameter do not need to be changed
for installing Oracle on Linux.
But you might want to adjust all shared memory settings later to optimize the server for Oracle.


Checking /tmp Space

The Oracle Universal Installer requires up to 400 MB of free space in
the /tmp directory.

To check the space in /tmp, run:

If you do not have enough space in the /tmp directory,
you can temporarily create a tmp directory in another filesystem. Here is how
you can do this:

When you are done with your Oracle installation, shutdown Oracle and remove the temporary directory:


Sizing Oracle Disk Space

You will need about 2.5 GB for the database software. If you perform
a typical database installation and not a customized database installation,
then you will need about 3.5 GB of disk space.


The “binutils” Issue

Skip this step for Oracle9iR2.

I did not experience this problem with
Oracle 9i (9.2.0), but only with Oracle 9i (9.0.1).

The binutils package that comes with Red Hat 7.1, 7.2, 7.3, and with
RedHat 2.1 Advanced Server doesn’t work with Oracle 9i (9.0.1) Universal Installer.
Here are the options you have for 9.0.1:

  • I do not recommend the following approach:

    Download the following binutil RPM version and downgrade binutil
    on the Oracle server:


    • ftp://ftp.redhat.com/pub/redhat/linux/7.0/en/os/i386/RedHat/RPMS/binutils-2.10.0.18-1.i386.rpm

    When you are done with the Oracle installation, you upgrade your binutil RPM back
    to the version you had before you downgraded. E.g. on the Red Hat 7.2 server I did:


Checking Development Packages (RPMs)

You will need some RPM development packages for the Oracle installer to build
the Oracle modules, otherwise you will get an error messages similar to this one:

Development Packages (RPMs) for RH 7.1, 7.2, and RH AS 2.1:

To see if these development packages are installed on your server, run the following command:

For instance, most of these packages will be missing when you installed RedHat 2.1 Advanced Server
and if you did not select the “Software Development” package. For the RedHat 2.1 Advanced Server
I executed the following commands to install the missing RPMs from the two CDs:

Development Packages (RPMs) for RH 7.3, 8.0, and 9:

To see if these development packages are installed on your server, run the following command:

For instance, when I installed Red Hat 9.0 and when I used the default packages for
the Installation Type “Server”, I had to install the following RPMs afterwards:

NOTE: Before you install Oracle9iR2 on Red Hat 9, make sure that you also read the information about the error message
“Error in invoking target install of make file /opt/oracle/product/9.2.0/network/lib/ins_oemagent.mk“
in the

Oracle Installation Errors section!

Development Packages (RPMs) for Red Hat Enterprise Linux Advanced Server 3 (RHEL AS 3):

To see if these development packages are installed on your server, run the following command:


JDK

Skip this step for Oracle9iR2.

I successfully installed Oracle9iR2 without installing JDK on the system.
Oracle comes now with its own Java. This means that you don’t have to execute the following
steps which were required for older Oracle versions:

Download JDK 1.3.1 or Blackdown 1.1.8_v3: (I usually used Blackdown)

http://www.blackdown.org

http://java.sun.com

According to the JDK documentation, install JDK under /usr/local.
Then create a symbolic link to the JDK under /usr/local/java:


Creating Oracle User Accounts

For more information on the "oinstall" group account, see

When to use “OINSTALL” group during install of oracle.


Creating Oracle Directories

In this example, make sure that the /opt filesystem is large enough, see

Oracle Disk Space for more information.

If /opt is not on a separate filesystem, then make sure the root filesystem
“/” has enough space.


Setting Oracle Environments

Set the following Oracle environment variables before you start runInstaller.

As the oracle user execute the following commands:

I successfully installed Oracle9iR2 without setting the following CLASSPATH environment variable:

You can put these environment settings at the end of the
~oracle/.bash_profile file
if you use bash. By this way you don’t have to set the environment variables again when you
login as “oracle”, or when you switch to the user “oracle” by executing “su - oracle“.


Starting runInstaller

Before you continue, make sure you have set the Oracle environment variables, see above.

Oracle no longer supports a character mode installer. Therefore, in order
to execute runInstaller directly from a console of a machine you are logged into
(in this example the node name where Oracle is running is called “oracleserver"),
you need to set the DISPLAY environment variable. Before you do that, make sure
that you also allow runInstaller on “oracleserver” to
display X information on your Linux desktop machine (in this example, the PC name where you
are running X Windows like KDE or GNOME is called “yourdesktop"),
because programs running on remote machines cannot display information to your screen unless
you give them the authority to do so. Note that the X display relink mechanism does not work
for NT desktop machines unless you use Exceed.

Before you run runInstaller, execute e.g. ‘xterm’ to see if your X setup is really working!
If you install Oracle on your desktop PC and not on a remote node, then you can skip step 1
and 3.

Step 1: Allow “oracleserver” to display X information to
your desktop PC “yourdesktop“:

Step 2: Open a new window and login to the Oracle server “oracleserver” as root.
This window will be used for mounting and unmounting the Oracle CDs.

Step 3: From the console of your Oracle server “oracleserver” where you will run
runInstaller, execute the following commands:

Step 4: Now execute runInstaller as “oracle”. Do not cd to /mnt/cdrom !!

NOTE:

Don’t run runInstaller for Red Hat Enterprise Linux Advanced Server 3 (RHEL AS 3) yet!
See

Running Oracle Installation on Red Hat Enterprise Linux Advanced Server 3
for more information.


Running Oracle Installation on RH 7.1, 7.2, 7.3, 8.0, 9, and on RH AS 2.1

Keep in mind that you will get one or more errors here during the Oracle installation!
See

Oracle Installation Errors for more information.

This is how I answered the questions for the runInstaller:

– What would you like as the base directory (Inventory Location):

– UNIX Group Name (permission for updating Oracle software):

– Full path name for Oracle Home:

etc.


Running Oracle Installation on Red Hat Enterprise Linux Advanced Server 3

In order to install an Oracle9iR2 database on RH AS 3, the “Oracle9iR2 Patch Set 3 9.2.0.4.0”
patchset and some other patches must be applied. Some errors can only be fixed by applying
the 9.2.0.4 patchset.

Installing Oracle9iR2 on RH AS 3

Install the following RPMs (see Oracle Note:252217.1 for more information):

Relink gcc so that the older gcc will be used during the Oracle installation (see Oracle Note:252217.1 for more information):

When you execute runInstaller from the Oracle 9iR2 (9.2.0) CD,
you will get the following error message:

To resolve the __libc_wait symbol issue, download the patch p3006854_9204_LINUX.zip from
http://metalink.oracle.com. See bug 3006854 for more information.

To apply the patch, run

NOTE: If you get the following error when you run rhel3_pre_install.sh:

Then you forgot to install or link gcc, see above. This means you can’t start any binaries any more:

To fix that, run the echo command which is a built-in shell command:

And start over again.

Now runInstaller can be started from the CD:

You may get the following errors:

Error in invoking target install of makefile /opt/oracle/product/9.2.0/network/lib/ins_oemagent.mk.

The /opt/oracle/product/9.2.0/install/make.log file reads:

Click ignore. This will be fixed by applying the patch 3119415 after the 9.2.0.4 patchset has been applied.
You won’t be able to apply the patch 3119415 at this time since the file
/opt/oracle/oraInventory/ContentsXML/comps.xml doesn’t exist yet.

Error in invoking target install of makefile /opt/oracle/product/9.2.0/ctx/lib/ins_ctx.mk.

The /opt/oracle/product/9.2.0/install/make.log file reads:

Click ignore. This is fixed by applying the 9.2.0.4 patchset.

Patching Oracle9iR2 on RH AS 3

To patch Oracle9iR2, download the Oracle 9i Release 2 Patch Set 3
Version 9.2.0.4.0 for Linux x86 from
http://metalink.oracle.com.

Copy the downloaded “p3095277_9204_LINUX.zip” file to e.g. /tmp and run the following command:

To patch the runInstaller, run:

To patch Oracle9iR2, run:

You may get the following error:

Error in invoking target install of makefile /opt/oracle/product/9.2.0/network/lib/ins_oemagent.mk.

The /opt/oracle/product/9.2.0/install/make.log file reads:

Click ignore. This will be fixed by applying the patch 3119415 after the 9.2.0.4 patchset has been applied.
The patch 3119415 cannot be applied while the patch process for the 9.2.0.4 patchset is running.

After the 9.2.0.4 patchset has been applied, download the patch p3119415_9204_LINUX.zip from
http://metalink.oracle.com. See bug 3119415 for more information.
Also, download the opatch Release 2.2.0 utility from
http://metalink.oracle.com.
See bug 2617419 for more information.

To install opatch, run:

Before you apply the 3119415 patch, you need to make sure the fuser binary can be found by the oracle user,
see the PATH environment variable below.
Otherwise the patch can’t be applied because the fuser binary is used by opatch.

To apply the 3119415 patch, run

Now you should be able to create a database with dbca:

Patching Oracle Intelligent Agent on RH AS 3

When you run "agentctl start" (Oracle 9.2.0.4), dbsnmp will crash:

To resolve this problem, apply the patch p3238244_9204_LINUX.zip from http://metalink.oracle.com.
See bug/patch 3238244 for more information.

Before you apply the patch, make sure the instance is down!

Also make sure the opatch script appears in your $PATH.
See
“Patching Oracle9iR2 on Red Hat AS 3”
for information on getting and installing opatch.
To verify if opatch is in your $PATH, run the which command:

To apply now the patch, run:

Now you need to relink dbsnmp. This is the binary that crashed when running agentctl start.
To find which makefile handles the linking of dbsnmp, you can run:

I relinked dbsnmp and all associated executables which are maintained by the ins_oemagent.mk makefile:

Now you should be able to start the agent:

NOTE: Don’t forget to undo the changes (links) to /usr/bin/gcc and /usr/bin/g++ if you
don’t need it any more. Also don’t forget the /etc/ld.so.preload file.


Startup and Shutdown of the Oracle 9i Database

sqlplus:

svrmgrl is not supported any more. You can now do everything with
sqlplus.

For instance, to startup the database, run the following commands:

The slash connects you to the schema owned by SYS. So in this example you will be
connected to the schema owned by SYS with the privilege SYSDBA.
SYSDBA gives you the following privileges:

  – sysoper privileges WITH ADMIN OPTION

  – create database

  – recover database until

$ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut

You can also use $ORACLE_HOME/bin/dbstart to startup the database, and
$ORACLE_HOME/bin/dbshut to shutdown the database. You can place
$ORACLE_HOME/bin/dbstart into the /etc/rc.d/rc.local boot script to
automatically bring up the database at system boot time. To get $ORACLE_HOME/bin/dbstart
and $ORACLE_HOME/bin/dbshut working, you need to change the third field for your Oracle
SID in /etc/oratab from “N” to “Y”.

For example, for the Oracle SID “test” I changed the line in /etc/oratab from:

to read:

In some cases for 9.2.0 I also had to copy the init file for my SID “test” from
/opt/oracle/admin/test/pfile to $ORACLE_HOME/dbs to get
dbstart and dbshut working:

But first make sure if your init file already exists in $ORACLE_HOME/dbs!


Oracle Installation Problems, Tips and Hints

Some of these problems apply only to 9.0.1!

  • Do not cd to /mnt/cdrom to run ./runInstaller!

    • If you do so, the installation will fail because you won’t be able to change the CDs.

  • If you forgot to set the DISPLAY environment variable (e.g. export
    DISPLAY=oracleserver:0.0)    , or if you forgot to give the remote console – your Oracle Server –
    authority to display X information on your desktop PC (e.g. xhost +oracleserver), then
    you will get the following error:

    • In this case, I always had to kill runInstaller in Oracle9iR1 (9.0.1) which was still
    running in the background. If I didn’t do this in 9.0.1, runInstaller didn’t completely come
    up any more without displaying any error messages. You might also want to clean up /tmp/OraInstall.

  • When runInstaller starts to configure the tools (“Configuration Tools”), the “Oracle
    Net Configuration Assistant” will sometimes hang. Simply stop the Assistant and restart it, or continue
    the installation. When the rest of the installation is finished, do a “Retry” for “Oracle Net
    Configuration Assistant”. This always worked for me.

  • When the system stops responding during the Oracle installation in particular during the database
    creation, then that’s probably because you don’t have enough RAM or enough swap space. I saw the
    whole system not responding or to “hang” for several minutes when I did not have enough swap space.
    If this happens, simply wait until the system starts to respond again.

  • If for any reason the Oracle9i installation didn’t finish successfully, you might want to clean
    up the following files and directories before you start over again:
    /etc/oraInst.loc /etc/oratab /tmp/<OtherOracleOwnedFiles> $ORACLE_BASE/*


Oracle Installation Errors

Here is a list of Oracle 9i (9.0.1 & 9.2.0) installation problems and issues.
Some issues, errors, problems, and solutions apply only to 9.0.1 and some only to 9.2.0. Since I did not experience all
of the problems here, I am not able to verify the correctness of all the solutions. However, I experienced
almost all of the problems listed here. If you have other problems and you were able to resolve them,
then please drop me an email at
webmaster_at_puschitz.com
so that I can add it to the list here.

Here is a list of issues issues, errors, problems and solutions:

  • Log Files

First check always the error logs for 9.2.0 in /tmp/OraInstall
(e.g /tmp/OraInstall2002-07-04_09-50-19PM), and for 9.0.1 in /tmp/OraInstall.
When you get make problems, check also the file $ORACLE_HOME/install/make.log.


  • “Various make Problems”

Make sure that gcc is installed on your system:

Here is the command to find the RPM package name for /usr/bin/gcc:

Check also the other error messages below.
See also

Development Packages for more information.



  • "Error in invoking target install of makefile /opt/oracle/product/9.2.0/ctx/lib/ins_ctx.mk"

I saw this error only when I installed Oracle9iR2 (9.2.0).
This was also the only problem I experienced with Oracle 9i R2 on Red Hat 8.0.
However, this does not necessarily mean that you won’t experience other problems described here.

When I had this problem, the following errors showed up in $ORACLE_HOME/install/make.log:

This error comes up when the following step is executed:

Edit the file $ORACLE_HOME/ctx/lib/env_ctx.mk, go to
“INSO_LINK =“,
and add a “$(LDLIBFLAG)dl” to the line and save it.

Here is the full line with the added “$(LDLIBFLAG)dl” flag:

INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m $(LDLIBFLAG)dl $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)

After that hit retry in the error popup.

If this didn’t work, then try the following:

Edit the file $ORACLE_HOME/ctx/lib/env_ctx.mk again, go to
“INSO_LINK =“, remove the above entry you made
and add a “cat $(LIBHOME)/sysliblist” to the line and save it.

Here is the full line with the added “cat $(LIBHOME)/sysliblist” string:

INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m cat $(LIBHOME)/sysliblist $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)

After that hit retry in the error popup.



  • ORA-27123: unable to attach to shared memory segment.

I saw this error only when I installed Oracle 9i R2 (9.2.0).

This error message came up when the Oracle Database Configuration Assistant was running.
I executed the following command to temporarily increase the maximum shared memory size:

Then click “Retry” for the Oracle Database Configuration Assistant.

It is recommended to increase the shmmax setting permanently for Oracle9i. So if
you want to increase the maximum shared memory size permanently, add the following line
to the /etc/sysctl.conf file:

For more information on setting shared memory parameters for Oracle, see

Setting Shared Memory.



  • ORA-03113: end-of-file on communication channel

I saw this error when I’ve run the “Database Configuration Assistant” and “sqlplus“.
When the “Database Configuration Assistant” gave me this error during Oracle9iR2 (9.2.0)
installation on Red Hat 2.1 AS, I simply removed the shared memory segments owned by the Oracle user
and I restarted the “Database Configuration Assistant”. I’m not sure if this is the right way but it always
worked for me. Here is what I did to get the “Database Configuration Assistant” running again:

Database Configuration Assistant:

I executed the ipcs command to get the address of the shared memory segments that have
been allocated by Oracle:

Then I removed all shared memory segments that were owned by the Oracle user during the installation with
the following command:

After that I restarted the “Database Configuration Assistant”. Once the installation was done I
immediately restarted the DB as well.

Caveat: I’m not sure if this procedure can cause any further problems if this is done during the installation.
But so far I haven’t seen any issues with this approach.

sqlplus:

If you get this problem in connection with sqlplus, then simply make sure that the database
is down and exit sqlplus. After that, follow the procedure above by removing all shared memory
segments that belong to the Oracle user. To my knowledge, this should not cause any problems.

For more information on shared memory segments, see

Determining Which Semaphore Sets and Shared Memory Segments Belong to Each Oracle Database or Instance.

NOTE:

To solve this problem permanently, increase the kernel shmmax size.
For more information, see

Setting Shared Memory and

Setting Shared Memory.



  • "Error invoking target install of makefile /opt/oracle/product/9.0.1/plsql/lib/ins_plsql.mk"

    "Error invoking target install of makefile /opt/oracle/product/9.0.1/precomp/lib/ins-precomp.mk"

    "Error invoking target install of makefile /opt/oracle/product/9.0.1/precomp/lib/ins-net-client"

I saw thi