Re: shutdown mmediate gets hung

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Mon, 31 Jan 2005 17:40:54 -0800
Message-ID: <1107221893.563996@yasure>

premmehrotra_at_hotmail.com wrote:

> DA Morgan wrote:
> 

>>premmehrotra_at_hotmail.com wrote:
>>
>>
>>>I am on oracle 8.1.6.2 on HP UNIX 11i.
>>>
>>>I am using following code to shutdown my database every Sunday:
>>>svrmgrl <<eof
>>>connect internal
>>>shutdown abort
>>>startup
>>>shutdown immediate
>>>exit
>>>This shutdown has been working fine until now, but this week end
>>>shutdown immedaite got stuck (see alert.log below):
>>>Sun Jan 30 15:06:31 2005
>>>Shutting down instance (immediate)
>>>License high water mark = 2
>>>Sun Jan 30 15:06:31 2005
>>>ALTER DATABASE CLOSE NORMAL
>>>Sun Jan 30 15:06:31 2005
>>>SMON: disabling tx recovery
>>>Mon Jan 31 05:33:08 2005
>>>
>>>Eventhough ALTER DATABASE CLOSE NORMAL was issued at 15:06:31, it

> 
> did
> 


>>>not shutdown the database.

>>>

>>>

>>>There was nothng running between startup and shutwon immediate.

>>>

>>>Can anyone tell me how to overcome this problem. I use

>>>shutdown abort (to force shutdown independt of anything running,

>>>then startup and then shutdown immediate...).

>>>

>>>

>>>Should I change startup to startup restrict eventhough I do not see

>>>that is the cause.

>>>

>>>

>>>

>>>Thanks a lot,

>>>
>>>Prem
>>
>>No DBMS_JOBs? No Advanced Queuing?
>>--
>>Daniel A. Morgan
>>University of Washington
>>damorgan_at_x.washington.edu
>>(replace 'x' with 'u' to respond)

>
> Yes, none of that. Looks like some bug in Oracle to me.

I highly doubt that so lets get real for a moment.

First you are running a Neolithic unsupported version of the Oracle database on an operating system for which I will guess it was never certified.

So how is this an Oracle bug?

Then it appears you are unlicensed or no longer have a support agreement or you'd have opened a TAR on metalink.

So how is this an Oracle bug?

But even if none of the above is true ... what is absolutely true is that Oracle 8.1.6.2 has been around for a very long time and this is the first time I have seen anyone complain about this so-called bug ... so maybe it is something person where the software just doesn't like you or your shoes. Perhaps?

<RANT>
Why is it that when people make pretty much every textbook mistake they can ... they call it a bug in the software? Is personal responsibility dead or just badly wounded? </RANT>

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)

Received on Mon Jan 31 2005 - 19:40:54 CST