Oracle 8.1.6 on RedHat 7.3

[kenny chia]

Hi
I have trouble with setting up a database in Oracle 8.1.6 with red hat 7.3 as the platform.

Here is the story
1. I installed oracle using the typical options
2. In the beginning, the installation proceeded smoothly.
3. Net 8 was automatically configured and succeded.
4. But during the demo database setup, there was a problem. After copying the datafiles from the disk, there was trouble starting up the database with the following error

"ORA-03113: End of file on communication channel "

here are my findings
1. There was no errors mentioned in all the log files.
2. The error occurred when this command is issued in svrmgrl.

startup nomount pfile = "/u01/app/oracle/admin/gene1/pfile/initdemo.ora"

My system spec
512M RAM
P4 2.6GHZ

[Bill Douglass]

Here is a tip sheet on installing Oracle on varions Linux versions:

http://www.puschitz.com/InstallingOracle9i.shtml

About 2/3 down the page, you'll see an entry covering the problem you are having.

This is Oracle 9i specific, but it looks like a similar problem to what you are having.

[Steven E. Protter]

I have run into the same error on 8.1.7 and 9i on Red Hat Linux versions 6.2 and 7.3

You have adequate memory, so don't worry about that.

Funny thing is that metalink says the problem was fixed in 8.1.7

I would consider downloading and installing it.

Makes sure swap is twice physical memory.

Increase the shared memory in the kernel. Compile and deploy the new kernel.

On your memory level, I would suggest shared memeory shmmax of 256 Megabytes.

Then you'll be okay.

SEP

[Steven E. Protter]

kenny,

Oracle's latest bug fixes for linux are in 8.1.7.0.1

http://otn.oracle.com/software/htdocs/devlic.html?/software/products/oracle8i/htdocs/linuxsoft.html

You'll need an otn id to access that link. Its free though.

Hope these posts helped.

SEP

[Indira Aramandla]

Hi,

The error basically means 'I cannot communicate with the Oracle shadow process'. As it is such a general error more information must be collected to help determine the true cause.

As the error is on STARTUP NOMOUNT:

Check the init.ora file used to start the database.This provides the configuration details used configure the instance. To help isolate the problem it may be useful use a very basic init.ora file when starting the instance. If this works then parameters can be increased / introduced one at a time to see if there is a problem with a particular
setting.

Ensure there is free disk space in:

a. Your USER_DUMP_DEST and BACKGROUND_DUMP_DEST locations

b. Your AUDIT destination (Unix) The default is ORACLE_HOME/rdbms/audit

c. Check the bdump and udump directories for the log. There may be a trc file: LGWR with some error code. in background process.
d. Check whether filesystem when redologs or archivelogs present are filled up.
Check your environment points at the expected ORACLE_HOME and ORACLE_SID and LOCAL is not set (NT registry).