Re: Problem when WIndows 2000 Server is rebooted

From: DA Morgan <damorgan_at_psoug.org>
Date: Sun, 13 Aug 2006 17:02:15 -0700
Message-ID: <1155513735.907466@bubbleator.drizzle.com>

dbaplusplus_at_hotmail.com wrote:

> Chuck Whealton wrote:

>> dbaplusplus_at_hotmail.com wrote:

>>> Chuck Whealton wrote:
>>>> dbaplusplus_at_hotmail.com wrote:
>>>>> DA Morgan wrote:
>>>>>> dbaplusplus_at_hotmail.com wrote:
>>>>>>> I am running Oracle 10.1.0.3 on Windows 2000 server. I have a few
>>>>>>> database instances. I have noticed that when Windows server is
>>>>>>> rebooted, once in a while (every 3 month or so). a database instance
>>>>>>> will not start properly. There are no error messages in alert.log file,
>>>>>>> however when one connects to database instance, it gives some error
>>>>>>> message.
>>>>>>>
>>>>>>> As I stated problem happens only once in a while and it is also not
>>>>>>> tied to a specific database instance (I have 3 instances). Has anyone
>>>>>>> seen similar problem and knows how to fix it in Windows 2000
>>>>>>> environment (I cannot move to UNIX, LINUX ...).
>>>>>>>
>>>>>>> Thanks.
>>>>>> Good advice from Sybrand and Chuck.
>>>>>>
>>>>>> But 10.1.0.3? Why? There is a patch to 10.1.0.4 that should be applied.
>>>>>> And as Sybrand points out: "some error message" is far from useful
>>>>>> information.
>>>>>> --
>>>>>> Daniel A. Morgan
>>>>>> University of Washington
>>>>>> damorgan_at_x.washington.edu
>>>>>> (replace x with u to respond)
>>>>>> Puget Sound Oracle Users Group
>>>>>> www.psoug.org
>>>>> 1. Reason  I cold not provide the error message is because no error
>>>>> message was written to alert.log file, so I could not emember the exact
>>>>> error message. Message probably was "databse recovery is in
>>>>> porgress....", but then I just shutdown the service and then restarted
>>>>> the service and instance started fine.
>>>>>
>>>>> 2. I cannot move to 10.1.0.4 because third party application was
>>>>> certfied only with 10.1.0.3.
>>>>>
>>>>> 3. I am not using ASM.
>>>> Alright, even though I kind of doubt this is your problem, if your
>>>> database is coming up requiring recovery that is somehow interfering
>>>> with it's startup (I'm surmising because I haven't had this particular
>>>> problem), perhaps it's not going down cleanly.  Maybe you should check
>>>> some of your Windows registry settings.  In particular, I'd look at
>>>> this URL:
>>>> http://www.databasejournal.com/features/oracle/article.php/3373301
>>>>
>>>> There are a couple Oracle registry entries in particular called
>>>> ORA_SID_AUTOSTART, ORA_SID_SHUTDOWN, ORA_SID_SHUTDOWNTYPE and
>>>> ORA_SID_SHUTDOWN_TIMEOUT that you may want to pay attention to.
>>>>
>>>> Remember that both Microsoft and Oracle advise you NOT to edit the
>>>> registry.  You may be able to use the ORADIM utility (I assume it's
>>>> also in 10g) to make any changes you might need, but hopefully somebody
>>>> will correct me if I'm wrong.
>>>>
>>>> Good luck...
>>>>
>>>> Charles R. Whealton
>>>> Charles Whealton @ pleasedontspam.com
>>> Chuck:
>>>
>>> Thanks a lot for provding useful information, Problem occurred again,
>>> and this time I found the error message:
>>> ORA-1033: Initalization or shudtown in progress....
>>>
>>> Basicaly Shutdown Immedaite is not shutting down the database
>>> completely (once in a while..), as a result during startup database
>>> does not start properly.
>>>
>>> I have changed ORA_SID_SHUTDOWNTYPE  to abort.
>>>
>>> In UNIX, when server is rebooted, I have a shutdown script for database
>>> which does:
>>> shutdown abort
>>> startup
>>> shutdown immediate
>>>
>>> Are there any hooks in Windows to do the same from Windows Service.

>> Well, I have to agree with Dan's post, which is that you need to find
>> out what's going on here. You shouldn't HAVE to do a shutdown abort.

>>

>> I understand the logic, if not the reasoning, why you do it the way you
>> are under UNIX. However, over there, you shouldn't need to do this
>> either. You know that UNIX has a couple of files called
>> $ORACLE_HOME/bin/dbshut and $ORACLE_HOME/bin/dbstart, right? I've
>> always just modified dbshut so it does a shutdown immediate.

>>

>> I think you've got some strange problems under Windows and it's
>> probably more important that you put your time into finding out what
>> that problem is, as opposed to searching for methodologies to mimic
>> what you're doing in UNIX, which isn't something you should HAVE to be
>> doing.

>>

>> Let me ask you this... on the UNIX box (which I know is not the object
>> of this thread). Do you have an application ON the UNIX system that
>> access the database? If so, you should ensure that the system is set
>> to shut that down first, before Oracle. This is usually accomplished
>> by adding the appropriate runtime symbolic links to call your generic
>> startup/shutdown script. During shutdown, it's before the DB and
>> during startup, after the DB is started. Forgive me if you already
>> know this stuff, but you'de be surprised the number of people who miss
>> it. If you don't have a generic startup/shutdown script for Oracle
>> under UNIX, you oughta get your hands on one. Under HP-UX I just
>> modified the generic template to do an remsh into the Oracle owner's
>> account, execute the Oracle owner's profile, and do a dbshut or
>> dbstart.

>>

>> As for Windows, I know of no straight forward way to accomplish your
>> shutdown abort/startup/shutdown immediate. Sorry... You really need to
>> diagnose the problem, but there is the chance what's going on could
>> lead to bigger problems down the road. How about what Dan mentioned?
>> Jobs running via Oracle's builtin job facility?

>>

>> Charles R. Whealton
>> Charles Whealton @ pleasedontspam.com

> 
> Chuck, Dan:
> 
> I used DBCA to create the database instance and it puts its own jobs
> (such as database statistics collection) and AQ. Yes, I do see messages
> related to AQ when shutdown immediate does not succeed. However, when I
> look at value of aq_tm_processes it is set to 0, so AQ should not be
> on.
> 
> I do not know what all Oracle's default instance creation does, but I
> do not know how to turn off AQ (if it is already not off).
> 
> My third  party application which uses Oracle 10g is also shutdown when
> server is rebooted, but I do not know how to ensure application is
> shutdown before Oracle. Third party application installs its own
> services (similar to Oracle). I do not think, it is application, which
> is causing problem.
> 
> 
> Appreciate any ideas.

When you are ready to perform a shutdown:

Look at gv$process and gv$session

You need to know what it is.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

Received on Sun Aug 13 2006 - 19:02:15 CDT