help: ORA-01034 Oracle not available

Darren Anderson

unread,

Jul 12, 2001, 10:00:42 AM7/12/01

to

Oracle 8.0.5 on NT on Intel;

We've been running this server for over a year in which time we've restarted
the server on many occassions without any problems. However, after
restarting it today, I'm getting "ORA-01034 Oracle not available" when
trying to connect to either of my DBs.

The LISTENER.ORA has not bee changed and looks fine, the listener service is
running as are the DB services.

Does anyone know why I'm getting this problem, especially given the fact
that nothing has changed on the server?

Darren.

TurkBear

unread,

Jul 12, 2001, 10:49:35 AM7/12/01

to

Here is a more detailed set of messages about this error:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ORA-01034ORACLE not available

Cause:ORACLE was not started up. Possible causes are:

·The SGA requires more space than was allocated for it.

·The operating system variable pointing to the instance is improperly defined.

Action:Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. Retry
after ORACLE has been initialized. If ORACLE has been initialized, verify that ORACLE was linked correctly. Also, refer to
the installation or user's guide for additional information about this error.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Also, the database service can be running without the instance being started..
Try

( from a cmd prompt )
set ORACLE_SID=[inset your sid name here]
svrmgrl
connect internal
startup pfile=[your init<sid>.ora file]

If it starts and opens ok, then the database itself has no problem ( like the lack of SGA space referred to in the above
messages) and the problem probably is in the registry settings for auto-starting the instance on startup of the service..

hth

"Darren Anderson" <darren....@uk.bosch.com> wrote:

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

Van Messner

unread,

Jul 12, 2001, 12:07:20 PM7/12/01

to

Accept my apologies if this answer seems trivial and this may not be your
case. You'll get that message if you try to connect to the server too
quickly after a restart. Wait ten or fifteen minutes and try again.

Van

"Darren Anderson" <darren....@uk.bosch.com> wrote in message
news:9ikagk$5es$1...@proxy.fe.internet.bosch.com...

Darren Anderson

unread,

Jul 13, 2001, 4:46:56 AM7/13/01

to

I tried what you suggested and the database Instances are up & accessible
again. Do you know why the Instances have stopped auto-starting whent the
server is restarted? What should I check in the Registry?

Thanks,
Darren

TurkBear

unread,

Jul 13, 2001, 9:46:41 AM7/13/01

to

I was afraid you were going to ask that...I'm not sure which registry entry
has the setting ( its been too long since I needed to change one)
, but I'm sure someone in this group will respond..

The sequence of startup actions can affect the ability to autostart the instance,
so be sure the listener is started before the database service -
However we have some installations where, no matter what the dba's try, the instance must be
individually started..

"Darren Anderson" <darren....@uk.bosch.com> wrote:

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----

Eric Fortin

unread,

Jul 13, 2001, 11:17:29 AM7/13/01

to

Before looking in the registry, did you check to make sure the init[].ora
file is pointing to the correct pfile?

"Darren Anderson" <darren....@uk.bosch.com> wrote in message

news:9imci1$jh6$1...@proxy.fe.internet.bosch.com...