Stopping the service will bring down everything. The annoying thing is that
it's just a random problem. It will work 99 out of 100 times. The shutdown
abort is part of my backup script: "shutdown abort, startup, shutdown" to
ensure a clean database before backup.
I've run an analyze on all table and indexes. No errors.
A shutdown abort will normally write to the alertxxxx.log file, bu tin my
case it doesn't, since it doesn't shut down.
BTW, Under NT4 SP4 this problem occurs more frequently than under NT4 SP3,
so I've reverted back to SP4.
--
Terry Dykstra
Canadian Forest Oil Ltd.
Ronald wrote in message <01HW.B2A704AE000466CF127E4B70_at_news.wxs.nl>...
>
>On Tue, 22 Dec 1998 19:18:57 +0100, Terry Dykstra wrote
>(in message <367fe1a7.0_at_news.cadvision.com>):
>>
>> I have one 7.3.4 database on my NT 4 server that occasionally refuses to
>> shut down when I use a shutdown abort. It just sits there. There are no
>> trace files, nothing in the alert log that shows any errors. My 7 other
>> instances never give me this problem, so I assume the database is
somewhere
>> corrupted. Any ideas on where to start looking for problems, corruption,
>> ...?
>>
>> -- Terry Dykstra (TeamPS) Canadian Forest Oil Ltd.
>>
>>
>Try 'startup force' This kills the instance, starts it up and performs
recovery
>when needed.
>--
>Ronald - Unix SA
>http://home.wxs.nl/~ronr/professional.html
> - Oracle DBA http://www.tresco.nl
> - Middleware programmer/
> designer mailto:R.Rood_at_tresco.nl
>
>
>
Received on Wed Dec 23 1998 - 14:48:33 CST
