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 -> Oracle8i Solaris x86

Oracle8i Solaris x86

From: Anthony Yu <pyrosius_at_pacbell.net>
Date: Sat, 14 Aug 1999 01:56:54 -0700
Message-ID: <37B52F56.81943997@pacbell.net>

I am encountering difficulties installing Oracle8i on Solaris 2.7 x86. Any help anyone reading this can offer would be appreciated.

At first the installation of the product goes along quite a bit more smoothly than the port for Linux, with files named correctly, no hassles with the JRE, et cetera. However, after the that portion completes and runs the Net8 Configuration Assistant apparently successfully, it fails when running the Database Configuration Assistant, which I assume is the same tool that can be run as dbassist post-install. Basically, what happens is it gets about halfway done according to the progress bar and then fails with ORA-01034: ORACLE not available.

A quick 'ps -ef | grep oracle' reveals
/usr/local/oracle8i/bin/tnslsnr LISTENER -inherent
as the only oracle process other than the installer running. Ignoring the error will cause the progress bar to inch up another couple of percent and then present the error again (several times). Running dbstart fails as well, though I don't believe I should have to do that considering this is a portion of the install. Is there something
I need to start, files I need to touch and/or edit, or some other solution
to the problem? I suspect it's an installer quirk, but still need to know
how to solve the problem.

Also, in the face of the idiosyncracies of the installer and failed installs which result from using it, what is the recommended way of cleanly uninstalling the product and of deleting halfway-created databases? Oracle seems to maintain some state between installs because even after removing /usr/local/oracle8i and
/usr/local/oraInventory

it remembers path names and believes the product is still installed. In the case of failed database creations (again because of ORA-01034) removing $ORAHOME/oradata/dbname also does not prevent dbassist from complaining that, say, 'testdb' exists even though it failed to install it last time.

Once again, any help would be much appreciated.

pyrosius_at_pacbell.net Received on Sat Aug 14 1999 - 03:56:54 CDT

Original text of this message

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