Re: Can't shutdown immediate ??

Let's get things straigt here:
Shutdown comes in three flavors
-normal : waits for everything to complete and users to log off and then shuts down.
-immediate : disallows new logons, and waits for active jobs/queries to complete (does NOT abort/rollback running queries) and then shuts down. -abort : kills all oracle processes which results in a shutdown.

If you want a shutdown to happen immediately without the chance of having to wait for active jobs to complete, the choice would be a shutdown abort. This is not a nice way to shutdown since it actually kills the processes that makes Oracle tick. To be safe you should do a shutdown abort, startup restrict (only DBA's can log on) and shutdown normal. This way, Oracle has the chance to do an instance recovery and clean up the remains of active transactions (ie a rollback).
Another way of accomplishing this is to issue a startup force, even when the database is already running. This will shutdown and startup the database immediately and do a rollback. A shutdown normal will shut the database down again and you don't have to worry about it coming up ok again.

Mike Philippens
http://www.oracle-home.com

Jerry Gitomer wrote:
>
>
> Okay, you issue a shutdown immediate. There is a batch job that has=20
> been running for two hours. It can take quite a while to roll it=20
> back. I worked on a system where a shutdown immediate was issued=20
> against a monthly load that had been running for over five hours - it=20
> took several hours to roll back ;-( and of course Oracle didn't shut=20
> down until the rollback was completed.
>
>
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
> On 4/28/00, 9:06:57 PM, feib <agi_at_feib.com.tw> wrote regarding Can't=20
> shutdown immediate ??:
>
>
> > Hello,there
 

> > I shutdown my db ( immediate) last night.
> > But db hanged, something in my alert file are follows
> > ......
> > .........
> > Fri Apr 28 23:00:03 2000
> > Thread 1 advanced to log sequence 3257
> > Current log# 2 seq# 3257 mem# 0: /dev/rrv_hd6_9_n1
> > Current log# 2 seq# 3257 mem# 1: /dev/rrv_hd7_9_n1
> > Fri Apr 28 23:00:11 2000
> > Shutting down instance (immediate)
> > License high water mark =3D 25
> > Fri Apr 28 23:05:13 2000
> > SHUTDOWN: waiting for active calls to complete.
>
>
> > "waiting for active calls to complete" ??
> > IMHO, when shutdown immediate Oracle server doenn't
> > wait for users currently connected to disconnect and rolls back
> > active transactions and disconnects all connected users.
> > Then closees and dismounts the db.
 

> > Why show me "waiting for active calls to complete" ??
 

> > My DB is 8.0.5 on RS/6000 with parallel server option.( 2=20
 nodes)
> > Is it related to OPS ??
 

> > Any idea ?
 

> > Best Regards,
> > Agi Chen

--
Posted via CNET Help.com
http://www.help.com/