Re: Can't shutdown immediate ??

        Okay, you issue a shutdown immediate. There is a batch job that has been running for two hours. It can take quite a while to roll it back. I worked on a system where a shutdown immediate was issued against a monthly load that had been running for over five hours - it took several hours to roll back ;-( and of course Oracle didn't shut 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 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 = 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
 nodes)
> Is it related to OPS ??
 

> Any idea ?
 

> Best Regards,
> Agi Chen
Received on Sat Apr 29 2000 - 00:00:00 CDT