Return-Path: Delivered-To: 2-oracle-l@orafaq.com Received: (qmail 6878 invoked from network); 6 Jun 2006 15:25:51 -0500 Received: from freelists-180.iquest.net (HELO turing.freelists.org) (206.53.239.180) by 69.64.49.119 with SMTP; 6 Jun 2006 15:25:51 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 10CBB34D87F; Tue, 6 Jun 2006 16:25:51 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21108-01; Tue, 6 Jun 2006 16:25:50 -0400 (EDT) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 7B8DA34D5AB; Tue, 6 Jun 2006 16:25:50 -0400 (EDT) Received: with ECARTIS (v1.0.0; list oracle-l); Tue, 06 Jun 2006 16:25:08 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id C9B7934CDD4 for ; Tue, 6 Jun 2006 16:25:08 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20916-02 for ; Tue, 6 Jun 2006 16:25:08 -0400 (EDT) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 423CC34D5AB for ; Tue, 6 Jun 2006 16:25:08 -0400 (EDT) Received: by nf-out-0910.google.com with SMTP id m19so15185nfc for ; Tue, 06 Jun 2006 13:25:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=VmX1QSui5fBRihN2+sQ3RpWHNgBF/5fTGth9FU0Yvk7GyHo8V/Us0d9O/TLPUx0Vd8Crak9GVEmwMUCXqtOhuCyJ4UVp6CeKFyOVJv0zFosvCRtk5K/6MSifjkAzLrSTe/qFcD5ghlD3k33ngFua/tCukWv/u8o4EQOgZtUOqpo= Received: by 10.48.143.17 with SMTP id q17mr25248nfd; Tue, 06 Jun 2006 13:25:07 -0700 (PDT) Received: by 10.48.42.13 with HTTP; Tue, 6 Jun 2006 13:25:07 -0700 (PDT) Message-ID: <910046b40606061325sf601bf4o8e9c8e8a3b2972f9@mail.gmail.com> Date: Tue, 6 Jun 2006 16:25:07 -0400 From: "Paul Drake" To: joseph.armstrong-champ@tufts.edu Subject: Re: windows database service not shutting down database on reboot Cc: oracle-l@freelists.org In-Reply-To: <4485DB92.6090501@tufts.edu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_341_15308899.1149625507401" References: <1148524233l.4017l.0l@medo.noip.com> <1148620931l.2807l.1l@medo.noip.com> <4485DB92.6090501@tufts.edu> X-archive-position: 35675 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: bdbafh@gmail.com Precedence: normal Reply-to: bdbafh@gmail.com X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at avenirtech.net ------=_Part_341_15308899.1149625507401 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/6/06, Joe Armstrong-Champ wrote: > > We have about 10 windows servers, some w2k, some w2003 with 9i and 10g > databases on them. When the server gets rebooted the database services > don't get stopped and the instances crash. They always recover on > startup and we have put a work-around in place but I'm curious about > whether anyone else has experienced this problem. The following message > appears in the oradim.log file when the problem happens: > > ORA-12638: Credential retrieval failed > > My guess is that a process which the database uses to authenticate > itself has stopped before the oracle service and that is why the > authentication fails. > > I have opened an sr but they are telling me to recreate the service > using oradim locally, not remotely. I did this but when it didn't work > they told me to apply the latest patchset and do it again. Since this is > happening across different oracle and windows versions I have a feeling > that it has nothing to do with the version. > > Has anyone else experienced this? > > Thanks. > Joe > -- > http://www.freelists.org/webpage/oracle-l > > > Joe, Did you do any mucking about in the registry regarding HKLM\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout The default value is only 20 seconds (20000), which was likely fine for a 7.3.4 database using say 128 MB of physical memory and perhaps a single job queue process. A 10g R1 database instance using say 1.7 GB of physical memory may take quite awhile to shutdown cleanly from a shutdown immediate. Perhaps the following would help: oradim -edit -sid mydb -shutmode a or if you don't want to go the route of shutdown abort when the serivce is stopped: oradim -edit -sid mydb -timeout 600 This won't help in the case of a hard shutdown (power-off by BOFH, ups runs out of juice, etc). It also won't help with your current symptoms. The re-create the serivce and apply the latest patchset are probably the first 2 lines off of their script for this issue. What credentials is the OS service running under? (localsystem, service account with membership in the local OS ORA_DBA group, service account with membership in the local OS ORA_MYDB_DBA group, etc) Paul ------=_Part_341_15308899.1149625507401 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/6/06, Joe Armstrong-Champ <joseph.armstrong-champ@tufts.edu> wrote:
We have about 10 windows servers, some w2k, some w2003 with 9i and 10g
databases on them. When the server gets rebooted the database services
don't get stopped and the instances crash. They always recover on
startup and we have put a work-around in place but I'm curious about
whether anyone else has experienced this problem. The following message
appears in the oradim.log file when the problem happens:

ORA-12638: Credential retrieval failed

My guess is that a process which the database uses to authenticate
itself has stopped before the oracle service and that is why the
authentication fails.

I have opened an sr but they are telling me to recreate the service
using oradim locally, not remotely. I did this but when it didn't work
they told me to apply the latest patchset and do it again. Since this is
happening across different oracle and windows versions I have a feeling
that it has nothing to do with the version.

Has anyone else experienced this?

Thanks.
Joe
--
http://www.freelists.org/webpage/oracle-l



Joe,

Did you do any mucking about in the registry regarding

HKLM\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout

The default value is only 20 seconds (20000), which was likely fine for a 7.3.4 database using say 128 MB of physical memory and perhaps a single job queue process.

A 10g R1 database instance using say 1.7 GB of physical memory may take quite awhile to shutdown cleanly from a shutdown immediate. Perhaps the following would help:

oradim -edit -sid mydb -shutmode a

or if you don't want to go the route of shutdown abort when the serivce is stopped:

oradim -edit -sid mydb -timeout 600

This won't help in the case of a hard shutdown (power-off by BOFH, ups runs out of juice, etc).
It also won't help with your current symptoms.

The re-create the serivce and apply the latest patchset are probably the first 2 lines off of their script for this issue.

What credentials is the OS service running under? (localsystem, service account with membership in the local OS ORA_DBA group, service account with membership in the local OS ORA_MYDB_DBA group, etc)

Paul
------=_Part_341_15308899.1149625507401-- -- http://www.freelists.org/webpage/oracle-l