database create tool (dbca) hangs on "creating instance" 9i
buckwheat
Did the install, then did a dbca/create database.
Let it default to everything, then it hung on "creating the instance".
Waited 30 mins, then aborted.
This left a process called "oracle" is still running, using about 90% cpu.
Only way to ice it is kill -9.
Tried this 9i install on another Sol8 machine, same results.
Now I can't believe I'm the only one having this problem - oh well, back to
8i
You know Oracle - you guys put buggy s/w like this on your download site.
You do this knowning full well the *only* people that will get it going are
those with "gold" support, and can call in to get the fix. So why put it
out there?
Not a dang thing on technet about this either.
"Howard J. Rogers" <howa...@www.com> wrote in message
news:3b93...@news.iprimus.com.au...
> Having just gone through much the same on Linux, I found the answer to my
> prayers to be to opt for a software install only, and then run dbca
> (Database Configuration Assistant) once the install was completed.
>
> Worked fine.
>
> Perhaps if you were in control of the process there might be some better
> indication of where it was failing.
>
> Just a thought.
>
> Regards
> HJR
>
>
> "buckwheat" <ace...@yahoo.com> wrote in message
> news:tYBk7.917$ZJ.3...@e3500-atl2.usenetserver.com...
> > 9i on Sol 8. Same box ran 8i no problems. Running the
create-a-database
> > assistant with user "oracle".
> >
> > I did all the "set SEMMNI=100..." in the /etc/system file.
> > ORACLE_HOME set correctly, in all shells.
> > Pre-install done per the manual, as was post-install.
> > Always hangs on "creating instance", even creating the instance is done
> > AFTER the creation of the DB files (like from a template).
> >
> > This one's got me stumped - any ideas?
> >
> > Thanks - Greg
> >
> > Sorry for xpost, unsure where it went
> >
> >
> >
>
>
Howard J. Rogers
> I tried that too.
> Did the install, then did a dbca/create database.
> Let it default to everything, then it hung on "creating the instance".
> Waited 30 mins, then aborted.
From my experiences just yesterday, I think you might be being a tad
impatient. Give it 2 hours, and then start frothing!
> This left a process called "oracle" is still running, using about 90% cpu.
> Only way to ice it is kill -9.
> Tried this 9i install on another Sol8 machine, same results.
>
> Now I can't believe I'm the only one having this problem - oh well, back
to
> 8i
>
If I can get it running on Linux, barely knowing one end of a grep from the
other, it's not an Oracle software issue. You said you checked the kernel
parameters ... what did you set ALL of them to?
Another thing you can try: go to $ORACLE_HOME/dbs and copy the default
init.ora to be initSID.ora (whatever your ORACLE_SID is set to, obviously).
Then fire up sqlplus, and try a startup nomount. See what errors you get
then (if it's the end of file on communication channel one, I'd strongly
suspect your kernel parameters or a permissions problem).
One more thing: you have the right version of the JRE? And you correctly
pointed to that during the install?
And finally... is this a "clean" Solaris installation, or are you
shoe-horning it into a previously-used box. No telling what's been set if
it's not clean, which might be a contributing issue.
> You know Oracle - you guys put buggy s/w like this on your download site.
> You do this knowning full well the *only* people that will get it going
are
> those with "gold" support, and can call in to get the fix. So why put it
> out there?
Like I say, it isn't buggy (well, this part of it isn't at any rate). It's
a darned sight more tricky than a mere Windows user is used to, but I've
found no need for a gold suport contract to get it working.
I guess I'm just saying that it's no good giving up at this stage: something
you are doing (or not doing) is causing the problem.
In case it helps, here is what Dave Haas posted here in response to my
please for help on Linux (so your paths might need to be different). I
followed the steps he outlined, and it worked (though I had also to remember
to set the kernel parameters first):
Quote on:
===================
To create mount points, simply use the mkdir command, like:
mkdir -p /oracle/mnt1 /oracle/mnt2 /oracle/mnt3
The -p option simply creates the upper directories if they don't already
exist (for example, the /oracle directory in the example above).
Now we would have to change the ownership of those directories (and the
group as well) to the oracle user, otherwise noone but root can write to
them.
chown oracle /oracle
chgrp dba /oracle
While we are on the topic of the oracle user, on Suse7.1 the Suse ppl have
already created the oracle account. You don't have to do it. According to
the install docs though, it says you are supposed to make the primary
group for the oracle user the oinstall group, and a secondary group the
dba group. That's bad advice. I would recommend switching those around:
usermod oracle -g dba -G oinstall
You probably want to change the password for the oracle account as well:
passwd oracle
So, you should have three directories plus the directory for the software
(something like the following, YMMV). Make sure all are owned by oracle
and the group is set to either oinstall or dba (I recommend dba, it makes
the db creation cleaner. If it's not dba then the background processes
have trouble writing trace files, etc)
/oracle/mnt1
/oracle/mnt2
/oracle/mnt3
/oracle/software
Log out of root and in as the oracle user. Then you set some evironment
variables (in .bashrc most likely):
export ORACLE_SID=xxxx
export ORACLE_BASE=/oracle/software
export ORACLE_HOME=$ORACLE_BASE/9i
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$ORACLE_HOME/bin:$PATH
and then start a new terminal for them to take effect. You can also put
them in .bash_profile if you want, it doesn't really matter.
Run the installer and you are off to the races.
===============
Quote off.
Hope it helps you as much as it helped me,
Regards
HJR
buckwheat
prob tonight. The first thing I did was ensure the system vars were
correct, then made sure permissions and groups were the way the manual said.
You do have a few items below that I did not try, so maybe that'll do it.
Now that you've got it going, how does it compare to 8?
Greg
Howard J. Rogers
No comparison with 8!
With 8i, it's trickier... do you *need* transactions to suspend when they
run out of space (9i)? Or can you live with them terminating and rolling
back? Do you use RMAN (because in 9i it *is* actually useable)? Do you use
Standby Database (because Data Guard in 9i makes that a viable proposition
now). And so on... in other words, a raft of great new features, but it all
depends on whether you need those features as to whether or not it's worth
upgrading.
Some features, however, I'd kill for.
I wouldn't go back to manky old manual rollback segments or temporary
tablespaces for love nor money now. And I've had a very pleasant afternoon
using the Flashback feature (it's 4 o'clock... what did the Emp table look
like at 1.30pm yesterday... hang on.... select * from emp ...result set is
as it was at 1.30pm yesterday!).
Neither would I particularly like to go back to the 'change init.ora
parameter...bounce instance....tune...change init.ora parameter....yet
another bounce' style of Performance Tuning. The ability to increase and
decrease the size of the components of the SGA on the fly is a godsend.
Generally, I think it's a good upgrade, and worth the effort (I get my
copies for free, though!). I hope you get it working soon.
Regards
HJR
"buckwheat" <ace...@yahoo.com> wrote in message
news:KuVk7.3541$VX3.2...@e3500-atl1.usenetserver.com...