On Mon, 19 Aug 2002 17:20:50 GMT, Daniel Morgan <dmorgan_at_exesolutions.com>
wrote:
>Ed Stevens wrote:
>
>> Subject: ora-27100
>>
>> Platform: Oracle 8.1.7.3.0 on NT 4, sp6
>>
>> I've searched the Google archives of this newsgroup as well as MetaLink and have
>> not found an explanation that fits my situation. All explanations for an
>> ora-27100 that I have been able to find point to a failed shutdown, almost
>> always on a unix box.
>>
>> Here's what I'm seeing . . .
>>
>> Shutdown immediate, works fine.
>> Warm reboot of the NT server
>> Startup the database, get an ora-27100
>> (operator failed to notice that database didn't start)
>> Several hours later I discover that database is not running, so connect and do a
>> normal startup, which completes with no problem.
>>
>> So . . . contrary to all of the explanations I've found for an ora-27100 . . .
>>
>> 1) I'm getting a clean shutdown, as evidenced in the alert log.
>> 2) Even if process WERE left hanging, the restart of the server (as
>> evidenced in the system event log) would have killed them
>> 3) When I discover that the DB failed to start, I am able to start it with
>> no corrective action, as if nothing had been wrong.
>>
>> --
>> Ed Stevens
>> (Opinions expressed do not necessarily represent those of my employer.)
>
>Sounds like a Windows services problem to me. There is certainly no harm in ....
>
>oradim -delete -sid <sid_name>
>
>oradim -new -sid <sid_name> -intpwd <sys password> -startmode a
>-pfile=<path_to_and_name_of_init.ora>
>
>Daniel Morgan
>
Hmm. Could this be the result of the operator firing up our "start databases"
script before the services have fully initialized? FWIW, I see this problem
every Monday morning (the db's and servers are re-cycled every Sunday morning)
on ONLY this DB. It is the only DB on this machine, but we have many others on
several other machines, all getting the same treatment.
--
Ed Stevens
(Opinions expressed do not necessarily represent those of my employer.)
Received on Mon Aug 19 2002 - 14:59:07 CDT
