Printable View
Dear all
I was installing Oracle 8.1.7 release 3 on Solaris 2.8 ( sun Sparc machine)
i took all cares before installing ( eve. variables etc and permissions)
installation proces went off smoothly linking too
but while creating database (starter database) in returned an error while initializing database ( not connected to oracle )
help.. where could I might have gone wrong
please help
thanks in advance
KP
Hi,
If you are trying to create database manually...
check $PATH is set properly in profile file.
and ensure init.ora is in correct location if not link to the location.
you can also check /usr/sbin/prtconf file is set to 555 permission.
Thanks.
Thanigaivasan
1. check ALRET.LOG file for discovering ur error.
(it place .../bdump/alertSID.log
2. in most cases it happen if u didn't setup Solaris kerner parameters in /etc/system file
check it, and compare with recomended values:
http://docs.oracle.com/database_mp_8i.html
(Oracle8i Release Notes, Release 3 (8.1.7) for Sun SPARC Solaris)
---------------------------------------------
SHMMAX 4294967295
SHMMIN 1
SHMMNI 100
SHMSEG 10
SEMOPM 100
SEMVMX 32767
---------------------------------------------
[Edited by Shestakov on 04-19-2002 at 04:51 PM]
well Shestakov,
Please correct me if I am wrong.
I was thinking kernel parameters required at the time of starting the database to allot the semaphores stuff like that.
(Ofcousre I generally follow while creating the database the following steps...
1.add kernel parameters..
2.reboot server
3.chmod 555 to prtconf
4.install oraclke software
5.edit profile .cshrc for the path
6.create database..so did not come across)
please advice.
Thanks.
Thanigaivasan.
Oracle installer don't use kernel parameters a lot, this is usual JVM application.
The kernel parameters use only when
ORACLE INSTANCE STARTED and
Oracle begin to use latchs, enqueue and so on ... (access to common resources and shared memory)
First command in database creation process (doesn't matter this is manual installation
or with using database assistent)
create database ...
this command MUST execute sql.bsq script.
and we ussualy get problems with unix kernel parameters.
[Edited by Shestakov on 04-19-2002 at 05:29 PM]
Thanks.
It clears me.
Thanigaivasan.