Re: Shutdown hangon.

Dear,
According your trace file and your command, there was some long transaction or pending/waiting transaction.
So 'shutdown immediate' waiting until that mysterious transaction ending. It can be casued by some user didnot commit his transaction or sessions.

In my case, I should try to find which session and the owner. And if it doesn;t matter to cancel/rollback, I use below step to stop DB:

1. shutdown abort
2. startup normal
3. shutdown immediate

I hope this can help you.
Regards,
"David Wang" <yuhang.wang_at_pek1.siemens.com.cn> wrote in message news:8tb3is$hpg$1_at_news.mch.sbs.de...
> Dear all,
>
> Yesterday, When I use the command -- shutdown immediate, the database is
> hangon for more than one hour. The database is very small even 100MB.
> Although I stop it by manually stop the basic service using the service
 icon
> in the control pane, I would like to know what is the reason and whether
 it
> will be damaged to my database, the following content is abstract from the
> trace file. Thanks for any responce to help me understand this trace file
> and the question I metioned,
>
> "
> Dump file D:\orant\RDBMS80\trace\ORA01844.TRC
> Thu Oct 26 08:27:59 2000
> ORACLE V8.0.5.0.0 - Production vsnsta=0
> vsnsql=c vsnxtr=3
> Windows NT V5.0, OS V8.147, CPU type 586
> Oracle8 Release 8.0.5.0.0 - Production
> PL/SQL Release 8.0.5.0.0 - Production
> Windows NT V5.0, OS V8.147, CPU type 586
> Instance name: orcl
>
> Redo thread mounted by this instance: 1
>
> Oracle process number: 17
>
> pid: 734
>
>
> *** SESSION ID:(15.13) 2000.10.26.08.27.58.997
> SHUTDOWN: waiting for active calls to complete.
> *** 2000.10.26.08.33.02.954
> SHUTDOWN: waiting for active calls to complete.
> "
>
>
>
Received on Fri Oct 27 2000 - 00:51:51 CDT