I installed Oracle9i on Suse Linux 7.1 (384MB RAM, 400MB
swap), and ran into a bit of a snag. The install ran fine
until the end when the database creation assistant attempted
to start the seed database. At that point I received an
"ORA-03113: End of File on Communication Channel" error, and
my Linux box froze up. Having Linux freeze up is a pretty
rare event in itself, but I'm really wondering what caused
the error. After rebooting, I was able to run the database
creation assistant, create another database, and start that
one. I then tried to manually start the seed database, and
received the same ORA-03113 error. Could this somehow be
related to memory? Was it too much to have the installer and
the creation assistant running at the same time?

A couple of other oddities I noticed:

During the install, I was asked to specify a location for
a JDK. I dutifully created a directory and typed in its
path, but the installer never actually put any files into
it. Why did it ask me for a directory that it wasn't going
to use?

When I run the oraenv script, it doesn't create an
ORACLE_HOME environment variable. Instead of adding
$ORACLE_HOME/bin to my path, it adds the full path to the
bin directory. Is $ORACLE_HOME going away?

Best regards,

Jonathan Gennick   
mailto:[EMAIL PROTECTED] * 906.387.1698
http://Gennick.com * http://MichiganWaterfalls.com * http://MetalDrums.org

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jonathan Gennick
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to