I used to have this problem, but ever since applying sp6a I don't think I've
ever had a problem with it.
I use oradim80 to shutdown, startup our 8.0.5.2.6 databases as part of our
nightly backup.
--
Terry Dykstra
Canadian Forest Oil Ltd.
"Leonard F Clark" <lfc_at_zoom.co.uk> wrote in message
news:3b435f94.12351140_at_192.168.0.1...
> Wayne,
>
> You don't say what kind of shutdown you were doing. I presume it was
> immediate. Was there a reason why, when you found the problem, you
> couldn't do a shutdown abort.
>
> Other reasons I've experience are:
>
> the disk containing archived redo logs filled up - but then you should
> get a message in the alert log (unless it's on the same disk);
>
> the disk containing key oracle files filled up.
>
> However, I would have thought that Oracle could point to these, if
> they are the culpret.
>
> It _could_ just be a space leak problem and, if so, you'd probably
> need to do a reboot anyway.
>
> Len
>
> >I'm running two production Oracle 8.0.6 DBs on a COMPAQ proliant 7000
> >server with NT 4.0 sp3.
> >Ram: 1GB
> >Processors: 2 Pentium II 500 mhz
> >
> >My problem is:
> >
> >I had been performing a cold backup every night and every few days
(perhaps
> >3 - 4 times a month one
> >DB would hang during the shutdown immediate process without any entry in
> >the alert_log to
> >give a clue as to WHY!
> >
> >To recover from this, I had to either reboot the server or more recently
I
> >used
> >TLIST to find which Oracel80.exe process corresponds to the crashed
database
> >and terminate it.
> >Then I can start the database normally...
> >
> >I experimented with using Oradim80 and svrmgr30 in my shutdown process
> >to see if one or the other could be the culprit, but the freeze has
occurred
> >with both.
> >
> >I tried changing my Temporary Tablespace from type "temporary" and
> >"permanent" to no avail...
> >
> >We were having this problem with Oracle 8.0.5 which was getting obsolete
so
> >I upgraded to 8.0.6 in hopes it
> > might resolve this problem... it didn't. ( The two applications I
support
> >are packages which interface with
> > each other and one has not been certified on 8i. The interface uses
DBLINKS
> >and so I'm forced to maintain
> >the two databases at the same Oracle version.)
> >
> >At one point I decided to try rebooting the NT server once a week, to
> >eliminate any potential memory leaks etc.
> >this also didn't have any impact on the problem...
> >
> >I queried just before shutdown for any active sessions which could be
> >causing the database to wait...
> >but have found none.
> >
> >My Oracle support has not been able to supply a solution besides "reboot
the
> >server when the problem occurs"
> >
> >At that point, I decided to give up trying for a bit and switch to hot
> >backups during the week...
> >
> >
> >My question:
> >
> >Has anyone else experienced a similar problem to mine? Any idea what
causes
> >it? How did you resolve it?
> >(Please don't tell me anything about doing shutdown aborts on a regular
> >basis... lol )
> >
> >
> >
>
Received on Sat Jul 21 2001 - 16:27:40 CDT
