Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Problem with "dbstart" script?
Hi,
Thank you! There *is* a problem with the "dbstart" script - I followed the instructions for the Enterprise Edition workaround and managed to get it fixed. Thank you once again!
In article <95651a$i1a$1_at_news.inet.tele.dk>,
"Ivan Bajon" <bajon_at_nospam@worldonline.dk> wrote:
> Hi,
>
> "dbstart" is bugged. It tries to figure out whether to startup using
> SQL*Plus or Server Manager by setting an environment variable
("version", if
> I remember correctly). Due to a bug in the script, this variable ends
up
> empty. Take a look at note 98418.1 on MetaLink.
>
> Hth,
> Ivan Bajon, ocp
>
> <briyani_at_my-deja.com> wrote in message
news:9562iv$l96$1_at_nnrp1.deja.com...
> > Hi all,
> >
> > I installed Oracle 8.1.6 (release 2) on Red Hat 6.2 and managed to
> > complete installation and log into the db successfully.
> >
> > However, I'm puzzling over starting up the database automatically
after
> > a system reboot. When I issue the command
> > "su - oracle -c $ORACLE_HOME/bin/dbstart"
> > upon startup to get the database going, I don't see the db
processes,
> > and I get the
> > ORA-01034: ORACLE not available
> > error when trying to connect to the database using sqlplus.
> >
> > I then tried running the dbstart command from my shell
interactively,
> > and I got the response
> > Database "TESTDB" warm started.
> >
> > which kinda tells me the script got executed and the db should be
> > started up. But as the above case, I still did not see any db
processes
> > running, and get the ORA-01034 error when I try to connect to the db
via
> > sqlplus.
> >
> > Finally, I then tried to start the database manually using svrmgrl.
That
> > worked, I finally get to see the db processes running and am able to
> > connect to the db via sqlplus.
> >
> > However, I still need to be able to startup the database when the
> > machine reboots via the /etc/rc.d/init.d files. Any ideas what could
be
> > the cause of the problem here? Could there be a problem with
"dbstart"?
> >
> > Thank you!!!
> >
> >
> > Sent via Deja.com
> > http://www.deja.com/
>
>
Sent via Deja.com
http://www.deja.com/
Received on Tue Jan 30 2001 - 19:28:18 CST