Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle 8.1.7 on Solaris installation problem

Re: Oracle 8.1.7 on Solaris installation problem

From: Rob Ratcliff <rrr6399_at_aa.net>
Date: Fri, 06 Oct 2000 02:52:08 GMT
Message-ID: <39DD3E0D.7225BB7D@aa.net>

 Well, I finally got the sucker working. It turned out that the ORA-03113 error was just a remnant of another underlying problem. It turned out that Oracle claimed in the installation documentation (pg. 2-2)
that the "PROCESSES" parameter in the initsid.ora file was set to 50 by default by the Oracle Database Configuration Assistant so SEMMSL should then be set to 60 and SEMMNS should be set to 110 in the /etc/system file. Well, after looking deeper into the problem, I found that the default database set the "processes" parameter to 150! so of course all my system kernel parameters were way off. I reset the "PROCESSES" to 45 and now everything works fine. I should've know it was some type of system configuration issue.

> Hi,
>
> I was wondering if anybody has had success installing the newest
> Oracle 8.1.7 release on Solaris. Being a Java programmer
> (no I'm not a DBA) I wanted to try out the new EJB 1.1 capability.
> I've had 8.1.6 running on this Solaris 2.7 (with all the latest patches
> applied) box without a problem in the past.
> (Just to make sure, I even deleted all the 8.1.7 related files and data
> and reinstalled 8.1.6 without any problems.)
>
> The installation goes fine until the installation program attempts to
> create a new starter database.
> For some reason its getting an error called:
>
> ORA-03113 end-of-file on communication channel
>
> If I use svrmgrl
> and do:
> connect internal
> startup
>
> or use dbstart
>
> I get the same error.
>
> This is what Oracle says about the error at
>
> ORA-03113 end-of-file on communication channel
>
> Cause: An unexpected end-of-file was processed on the communication
> channel; bug could not be handled by the SQL*Net (two task) software.
> This message could occur if the shadow two-task process associated with
> a SQL*Net connect has terminated abnormally or there is a physical
> failure of the interprocess communication vehicle (that is, the network
> or server machine went down).
>
> Action: If this message occurs during a connection attempt, check the
> setup files for the appropriate SQL*Net driver and confirm SQL*Net
> software is correctly installed on the server. If the message occurs
> after a connection is well established and the error is not due to a
> physical failure, check if a trace file was generated on the server at
> failure time. Existence of a trace file may suggest an ORACLE internal
> error that requires the assistance of Worldwide Customer Support.
>
> I'm not using Oracle naming or anything fancy.
>
> One thing Oracle needs to do is to make the installation process a
> little finer grained.
> Since I'm not familiar with the bowels of Oracle, any time the
> installation process fails
> I have to delete everything and start over from scratch.
>
> Anyway, it'd be great to know if anybody has had the same problems as I
> so I know that
> its not just my particular machine.
>
> Thanks,
>
> Rob Ratcliff
Received on Thu Oct 05 2000 - 21:52:08 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US