Received: by 10.66.80.4 with SMTP id n4mr72030pax.7.1352240992214;
        Tue, 06 Nov 2012 14:29:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.131.8 with SMTP id oi8mr895423pbb.15.1352240992195; Tue, 06
 Nov 2012 14:29:52 -0800 (PST)
Path: s9ni82046pbb.0!nntp.google.com!kt20no34381796pbb.1!postnews.google.com!i2g2000pbi.googlegroups.com!not-for-mail
Newsgroups: comp.databases.oracle.server
Date: Tue, 6 Nov 2012 14:29:52 -0800 (PST)
Complaints-To: groups-abuse@google.com
Injection-Info: i2g2000pbi.googlegroups.com; posting-host=64.58.150.28; posting-account=tpQovAkAAABNoH5bwsZAiff2L0zxGwdv
NNTP-Posting-Host: 64.58.150.28
References: <965cd36d-f12b-4799-b4f5-4f9c0c88ae84@googlegroups.com> <0b417270-c41f-4631-a001-1d41cc022355@googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0,gzip(gfe)
Message-ID: <f41ce9f6-2acc-40a7-b614-391a5a101508@i2g2000pbi.googlegroups.com>
Subject: Re: Unable to shutdown the database
From: joel garry <joel-ga...@home.com>
Injection-Date: Tue, 06 Nov 2012 22:29:52 +0000
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Nov 2, 8:04=A0pm, zigzag...@yahoo.com wrote:
> On Friday, November 2, 2012 3:46:22 AM UTC-4, zigz...@yahoo.com wrote:
> > I am on Oracle 11.1.0.7 on HP UNIX 11i. I have been using following pro=
cedure to shutdown database for a long
>
> > time:
>
> > 1. shutdown abort
>
> > 2. startup
>
> > 3. shutdown immediate
>
> > Today (after Sandy hurricane where my datacenter lost network connectiv=
ity), I noticed:
>
> > In the last step, database does not close, I have been waiting for 30 m=
inutes and gave up. My database is only 50GB.
>
> > Any idea, why?
>
> > When I could not do step 3, I did again following steps:
>
> > 1. shutdown abort
>
> > 2. startup
>
> > Database comes up and I do not see any errors. I can access all my data=
. Can anyon eexplain, database will not shutdown without abort(why I have t=
o wait forever, how I can troubleshoot).
>
> As I said earlier, because of Sandy storm, my site =A0where database and =
app servers are installed =A0 lost wide area network connectivity. As a res=
ult I could not remotely logon to database server. Then inside the site, so=
meone managed to connect using UNIX server console. Then the person was try=
ing to shutdown oracle and restart it. We have scripts which were developed=
 to be called from UNIx=92s /sbin/rcx.d =85when server reboots. Even though=
 we =A0were not rebooting the server, we were using those scripts to recycl=
e oracle and shutdown was getting hung.
> Today, our WAN connectivity was restored, so I could logon to DB server r=
emotely and wow I could do all the three steps in 2-3 minutes and shutdown =
immediate completed in a minute instead of =93hanging=94 =A0even after =A03=
0 minutes.
> May be, UNIX server was somehow trying to connect through wide area netwo=
rk while shutdown immediate was going on.. I do not know why it will need t=
o go through =A0WAN when Oracle is being shutdown=85; but restore of WAN ma=
de all the difference. All my disks on db server are =93local=94; i.e., we =
do not use SAN in this site.

If you have an rman backup going from somewhere else, it may be
possible for it to spawn parallel processes, which continue to try to
communicate with the parent that is no longer reachable.  These oracle
processes would ignore a kill session command, requiring death from
the OS.   I know I've seen this locally, when the parent is
accidentally killed, I'm speculating about WAN.  But you could try it
if you have a suitable test setup, and it could possibly apply to any
parallelization operation.

> Thanks a lot for your insight on different ways of shutting down. I have =
read at few places, there is nothing wrong with =A0shutdown abort (other th=
an users uncommited work will be interrupted) and =A0then doing =A0startup =
and then shutdown =A0immediate . You will not =A0 risk =A0your database in =
anyway by doing 3 steps. Instead of just one step shutdown immediate.

Remember, most of those are simply quoting each other, some are "he-
man" implying you are a scaredy-cat to be afraid of shutdown abort and
that it can't be a problem if they've never seen a problem, and some
simply don't acknowledge bugs or extreme situations for educational
purposes.  The one you've pointed at is certainly out of date.

jg
--
@home.com is bogus.
https://plus.google.com/photos/106910392693696947072/albums/537488021616983=
9969/5781744200831793442