Shutdown immediate problem

I'm trying to shutdown an Oracle9i database on Unix using SHUTDOWN IMMEDIATE but it just hangs.
I checked the sessions in V$SESSION and noticed there were a few INACTIVE sessions. So I built a script that goes thru all the INACTIVE sessions and kills them.
With all these sessions having status KILLED...when I try to run a SHUTDOWN IMMEDIATE, the database still hangs. I don't want to use SHUTDOWN ABORT.
Does anyone have any information on what makes SHUTDOWN IMMEDIATE hang? Could there be some unix processes....or oracle processes?
Thanks

Dear All,
I am also having some shutdown problem with the Oracle 10g on my Windows Server 2003 machine. My machine could not shutdown (means OS cannot completely shutdown the machine) even after i issued the "shutdown immediate" command.
As what Jaafar said, we should kill the process from OS level. Can any of you explain more on this as I have no idea on how to do this? Which process should I kill after I issued the "Shutdown immediate" command?
Thank you.
best regards,
Wnson

Similar Messages

Shutdown immediate - will be a problem?

I need to shutdown Oracle database. I wonder if I can do it cleanly? The problem depends on that there is a session 497 which can't be killed neither on database level nor os level. (On database level it simultanously expires and starts with new serial, on os level there is no process related to this session, or it can be zombie process we have, which can't be killed too) Session 497 is probably related to badly canceled operation of bringing a datafile online. Sometime ago we had to bring a datafile online so media recovery of this datafile was required. As we had no archivelog (21 days window) the media recovery couldn't be acomplished. This operation hung. Session 497 may still want to recover that datafile. How do you think? May any problems occur during a shutdown process? May shutdown immediate process wait (and hang too) untill the 497 session end?
Edited by: Przemek Piechota on 2011-02-10 07:40

content of alert_log:
Wed Feb 9 00:29:58 2011
ORA-1157 signalled during: ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE...
Wed Feb 9 00:33:20 2011
ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE
Wed Feb 9 00:33:20 2011
Errors in file /u01/app/oracle/admin/easy/bdump/easy1_dbw0_1028264.trc:
ORA-01157: Message 1157 not found; No message file for product=RDBMS, facility=ORA; arguments: [74]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [74] [u01/app/oracle/oradata/easy/integracja03]
ORA-27037: Message 27037 not found; No message file for product=RDBMS, facility=ORA
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Wed Feb 9 00:33:20 2011
ORA-1157 signalled during: ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE...
Wed Feb 9 00:47:46 2011
Thread 1 advanced to log sequence 51550 (LGWR switch)
Current log# 1 seq# 51550 mem# 0: /u01/app/oracle/oradata/easy/log1a
Current log# 1 seq# 51550 mem# 1: /u01/app/oracle/oradata/easy/log1b
Wed Feb 9 01:01:41 2011
ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE
Wed Feb 9 01:01:41 2011
ORA-1113 signalled during: ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE...
Wed Feb 9 01:03:58 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:03:58 2011
Media Recovery Start
parallel recovery started with 3 processes
ORA-279 signalled during: ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03' ...
Wed Feb 9 01:05:28 2011
ALTER DATABASE RECOVER CANCEL
Wed Feb 9 01:05:29 2011
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Wed Feb 9 01:05:29 2011
ALTER DATABASE RECOVER CANCEL
Wed Feb 9 01:05:29 2011
Errors in file /u01/app/oracle/admin/easy/udump/easy1_ora_1843296.trc:
*ORA-07445: exception encountered: core dump [kcrpnq+006c] [SIGSEGV] [Invalid permissions for mapped object] [0x000000000] [] []*
Wed Feb 9 01:05:30 2011
*Trace dumping is performing id=[cdmp_20110209010530]*
Wed Feb 9 01:10:20 2011
PMON failed to delete process, see PMON trace file
Wed Feb 9 01:16:31 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:16:31 2011
Media Recovery Start
Wed Feb 9 01:16:31 2011
Media Recovery failed with error 1124
ORA-283 signalled during: ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03' ...
Wed Feb 9 01:17:29 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:17:29 2011
Media Recovery Start
Wed Feb 9 01:17:29 2011
Media Recovery failed with error 1124
Wed Feb 9 01:42:04 2011
Completed: alter database datafile '/u01/app/oracle/oradata/easy/integracja03' offline drop
Wed Feb 9 01:43:53 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:43:53 2011
Media Recovery Start
Wed Feb 9 01:43:53 2011
Media Recovery failed with error 1124
ORA-283 signalled during: ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03' ...

Shutdown immediate hanging

I need to develop a scripts that shuts down all databases on a server. One of my databases sometimes hangs after issuing "shutdown immediate" command, and I want to handle this situation in my script. What I am thinking is to add "shutdown abort" in the script if "shutdown immediate" does not work. However, I do not know how to determine the database is hanging during shutdown immediate. Can you advise me on how to handle the shutdown immediate hanging problem in my shell script? Or is there better way to handle this in the script?
Thank you very much for your help!

As noted, if your shutdown immediate really hang because of rollback, then my method won't work either. The only different will be Oracle is going to do the rollback at next startup when doing instance recovery. In that case, the startup will appear to be hang.
Check this metalink doc,
What To Do and Not To Do When 'shutdown immediate' Hangs
Doc ID: Note:375935.1
There are cases where shutdown immediate hang because of bug.
Shutdown Immediate Hangs
Doc ID: Note:268884.1

Shutdown immediate hangs

SunOS 5.8
Database version: 9.2.0.4.0
Customer shutdown database every night for backup the datafiles to disk.
For your information, 2 weeks ago customer moved datafiles to a new disk.
The stoppscript has worked for a week.
And after a week the database will not shutdown.
We did a shutdown abort, and it works for a couple of days.
Now it happend again. The database will not go down.
Can't find any error messages!
Any suggestions?
# stoppscript
. $HOME/.profile
INSTANSER="BALA"
echo
echo "###########################################"
echo "# Startar nedtagning av O R A C L E #"
echo "###########################################"
echo
echo
echo "####### Stoppar LISTENER #######"
echo
$ORACLE_HOME/bin/lsnrctl << EOF
stop LISTENER
exit
EOF
for i in $INSTANSER
do
ORACLE_SID=$i
export ORACLE_SID
echo
echo "##### Stoppar instans - $ORACLE_SID #####"
echo
$ORACLE_HOME/bin/sqlplus /nolog << EOF
connect / as sysdba
shutdown immediate
startup exclusive restrict
shutdown
exit
EOF
done
echo
echo "########################################"
echo "# Slut nedtagning av O R A C L E #"
echo "########################################"
echo
# Alert_log
Tue Sep 5 01:16:48 2006
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 41
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Tue Sep 5 01:16:55 2006
ALTER DATABASE CLOSE NORMAL
Tue Sep 5 01:16:55 2006
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Sep 5 01:16:56 2006
Shutting down archive processes
Archiving is disabled
Tue Sep 5 01:16:56 2006
ARCH shutting down
ARC0: Archival stopped
Tue Sep 5 01:16:56 2006
ARCH shutting down
ARC1: Archival stopped
Tue Sep 5 01:16:56 2006
Thread 1 closed at log sequence 11287
Successful close of redo thread 1.
Tue Sep 5 01:16:56 2006
Completed: ALTER DATABASE CLOSE NORMAL
Tue Sep 5 01:16:56 2006
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Sep 5 08:15:15 2006
Shutting down instance (abort)

I am having similar problem. My server has been up for around 100 days now. And I extensively use XML DB in my code. So, now the DOM memory failed for me, so, I am doing shutdown immediate in the hope that it might fix it ( or atleast start where it is hanging).
Here is a snippet of my alert log file. Can you see where I am stuck at?
Thu Sep 21 14:01:15 2006
Process m001 died, see its trace file
Thu Sep 21 14:01:15 2006
ksvcreate: Process(m001) creation failed
Thu Sep 21 14:28:38 2006
Starting background process EMN0
EMN0 started with pid=19, OS id=2396
Thu Sep 21 14:28:38 2006
Shutting down instance: further logons disabled
Thu Sep 21 14:28:40 2006
Stopping background process CJQ0
Thu Sep 21 14:28:40 2006
Stopping background process QMNC
Thu Sep 21 14:28:42 2006
Stopping background process MMNL
Thu Sep 21 14:28:43 2006
Stopping background process MMON
Thu Sep 21 14:28:45 2006
Shutting down instance (immediate)
License high water mark = 23
Thu Sep 21 14:28:45 2006
Stopping Job queue slave processes
Thu Sep 21 14:28:45 2006
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Thu Sep 21 14:28:55 2006
ALTER DATABASE CLOSE NORMAL
Thu Sep 21 14:28:55 2006
SMON: disabling tx recovery
SMON: disabling cache recovery
Thu Sep 21 14:28:56 2006
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 411
Successful close of redo thread 1
Thu Sep 21 14:29:01 2006
Completed: ALTER DATABASE CLOSE NORMAL
Thu Sep 21 14:29:01 2006
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
btw, This is my screen right now.
U:\Rahul\sql>sqlplus sys as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Sep 21 14:28:16 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Release 10.2.0.1.0 - Production
SQL> sho sga
Total System Global Area 436207616 bytes
Fixed Size 1249440 bytes
Variable Size 142610272 bytes
Database Buffers 289406976 bytes
Redo Buffers 2940928 bytes
SQL> shutdown immediate;
Database closed.
Database dismounted.
Ok, when I am writing this post, I came back with this message.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 436207616 bytes
Fixed Size 1249440 bytes
Variable Size 142610272 bytes
Database Buffers 289406976 bytes
Redo Buffers 2940928 bytes
Database mounted.
Database opened.
SQL>
Still, any comments would be really appreciated.
Thank you,
Rahul.
P.S - This is a 32 bit windows 2003 server. 10gR2.
Message was edited by:
rputtagunta

Shutdown immediate won't work, Must abort to switch to SunCluster standby

Customer has a Solaris Clusterware, The customer sees the semtimedop() system call returning EAGAIN when running "shutdown immediate" on their database on one cluster node. This is expected when the shared resource that the semaphore is protecting is unavailable. The shared resource is only being used by Oracle processes, so we need to know what the resource is and what the other processes are doing with it. MOS doc 760968.1 isn't helpful. A Solaris crash dump taken when the database shutdown problem was occurring showed no signs of an OS issue so database assistance is needed.
We have tried to capture the following trace, but the trace is empty , and we 're stuck since then.
SQL> alter session set events '10046 trace name context forever,level 12';
SQL> alter session set events '10400 trace name context forever, level 1';
SQL> shutdown immediate;

don't you think it is about time you upgraded to something that hasn't been out of support since 2007 (almost 6 years ago...???). Hopefully you don't have any CC information stored in that db as there has not been any security updates since before it went to de-support.
What I would like to know is how did you even get 9i to install on Solaris 10? IIRC, that is not even a supported OS/Oracle version configuration. As for your current problem,
http://www.lmgtfy.com/?q=oracle+9i+suncluster+failover
http://docs.oracle.com/cd/E19787-01/820-2574/gctbk/index.html

Database shutdown immediate - time calculation ?

Hi,
Good Day.
did any one tried to calculate time the database would took to complete "shutdown immediate" command?
hope to have a healthy discussion..
Regards,
Muhammad Ahmad

Mohamed ELAzab wrote:
Hello Jonathan Lewis,
1-Please note that looking into the alert_sid.log is a good start as it will show if the smon process was dead according to the note:
Shutdown Normal or Shutdown Immediate Hangs. SMON disabling TX Recovery [ID 1076161.6]
I can see that that note is labelled: "Checked for relevance June 2009", but have you seen the garbage it suggests for temporary segments:
<ul>
Verify that temporary segments are decreasing
To verify that the temporary segments are decreasing have an active session
available in Server Manager or SQLPLUS during the SHUTDOWN IMMEDIATE. Issue the following
query to ensure the database is not hanging, but is actually perform extent
cleanup:
SVRMGR/SQL> select count(block#) from fet$;
COUNT(BLOC
+7+
SVRMGR/SQL> select count(block#) from uet$;
COUNT(BLOC
+402+
</ul>
For this to be true the temporary tablespace would have to be declared as dictionary managed, possibly even with contents = "PERMANENT" but it's so long since I've created a dictionary-managed TEMP that I can't be sure of the second point. I would be very cautious about trusting any document that started with such antiquated material - you can have no idea how much of its content might be (at best) deficient and (at worst) dangerously wrong.
3-to know the transactions that will be rolled back please read the note:
How to Check Why Shutdown Immediate Hangs? [ID 164504.1]
Same type of problem - "Checked for relevance: Mar 2010", starts with:
<ul>
Start Server Manager (or SQL*Plus for 8i or higher)
SVRMGRL> connect internal (or SYSDBA for 8i or higher)
SVRMGRL> select * from x$ktuxe where ktuxecfl = 'DEAD';
</ul>
Although x$ktuxe will show you transaction states from the undo segment headers, and this might show you recursive (or other special case) transactions that do not appear in v$transaction, I wouldn't trust a note that is based on 7.3 technology to be an appropriate reference document.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Shut immediate problem

Hi all,
I have problem while shutting down the database..
shutdown is in hang state and i got the below message in alert log
alertLog
Waiting for smon to disable tx recovery.
please suggest me the solution for the same

Hi,
According to Note:375935.1, this kind of situation is mostly caused by 2 things:
1. a large query running at the shutdown moment.
2. a large transaction running at the shutdown moment.
So, before issuing the shutdown immediate, it would be recommended to check the following views, especially when the database needs to be brought down for a very short period of time:
1. for large queries:
select count(*) from v$session_longops where time_remaining>0;
2. for large transactions:
select sum(used_ublk) from v$transaction;
1. For the large queries situation, when the shutdown immediate is hanging, you can just bring down the database using: shutdown abort, as the database could be easily brought to a consistent state by:
startup restrict followed by shutdown immediate.
One should take the backup and/or do whatever else need to be done after the shutdown immediate.
2. For the second situation, the workaround cannot be applied, especially when it's needed to take a cold backup. The database must be closed in a consistent state in order to do this and the consistent state cannot be achieved until all the transactions have completed one way or another (commit/rollback).
Cheers

Shutdown immediate fails

Hi Gurus,
since Saturday I got a problem with my Oracle 10g. I cannot shutdown it anymore with shutdown immediate (runs without finishing), and when I shut it down with shutdown abort and restart it, it runs recovery, and afterwards it runs very slowly. Especially connections from outside do not work at all (via thin client), they are so slow that I get timeouts.
Please help, I don't have any idea any more!
Bye,
Daniel

As you've done a SHUTDOWN ABORT and STARTUP, you would be able to monitor the rollback that it is attempting by querying V$FAST_START_TRANSACTIONS after the startup.
UNDOBLOCKSTOTAL is the number of Undo Blocks that have to be applied in the rollback.
UNDOBLOCKSDONE is the number of Blocks done so far.
Thus UNDOBLOCKSDONE*100/UNDOBLOCKSTOTAL is the percentage done.
There are times when the Instance Recovery is slowed down by FAST_START_PARALLEL_ROLLBACK.
You could set the instance parameter FAST_START_PARALLEL_ROLLBACK to FALSE and restart the instance and watch the speed of the rollback in v$FAST_START_TRANSACTIONS. (obviously, you'd need to SHUTDOWN ABORT and STARTUP, else the SHUTDOWN would wait for the "slow" rollback to complete).
Hemant K Chitale
http://hemantoracledba.blogspot.com

Shutdown immediate taking time

HI
I m using oracle 10g release 2. on hpux itanium
some of my database is taking longer time to shutdown more than 30 minutes. so usually i m doing
startup force and than shutdown immediate... wat is the problem behind this and how can i resolve it plz suggest.

A SHUTDOWN NORMAL will wait for sessions to disconnect. So, if you have application processes or users that do not disconnect, it will "hang". It is likely that this is causing your shutdown to delay. You could check the alert log file for messages about Oracle waiting for users to disconnect.
A SHUTDOWN IMMEDIATE will kill active sessions, complete a rollback of transactions that are killed and then shutdown the database. If you are using a SHUTDOWN IMMEDIATE, this can take a long time if there are large active transactions (or many active transactions) that Oracle needs to rollback -- the rollback can take time. (Also, if there are very many connected sessions, Oracle will take time to disconnect all of them).
A SHUTDOWN ABORT does a quick kill by shutting down the instance, without validating connected sessions. Rollback is automatically initiated by Oracle with the Instance Recovery at the STARTUP. The STARTUP can take slightly longer (in terms of seconds or a few minutes, generally) depending on the volume of Redo to be re-applied. Rollback is deferred to be executed after the OPEN.
You could try a SHUTDOWN TRANSACTIONAL. However, this can still take a long time or "hang" if a user or application process (or multiple of them) has/have active transaction(s) and does/do not issue COMMITs.
See the documentation on the SHUTDOWN command :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14357/ch12042.htm#i2699551
Hemant K Chitale
http://hemantoracledba.blogspot.com

Itunes won't open get an immediate problem window please help

I just recently did a complete system restore and have since got everything back together. I just tried last night to re-install intunes first with the start up disc and then through the itunes site. After both times downloading the program with no problems I went to start itunes and get an immediate problem screen. The problem only states "itunes has encountered a problem and needs to close. We are sorry the inconvenience" with no explantion or way to correct. Any help would be greatly appreciated.
Thank you,
Lawrence

I have been having the same problem lately. I have not found a solution yet. I've tried repairing the disk, reparing permissions, using a different user, reinstalling itunes, trashing the .plist, but nothing has worked. After iTunes is launched it immediately becomes unresponsive and will not Force Quit. Any help would be appreciated. Thanks.

Scheduled shutdown immediate and full database export

Hi all,
The database is Oracle 10g.
How to make a scheduled shutdown immediate and full database export ? I want to use a batch file for it so I can make a sheduled task from the windows control panel everyday at 2 am. So what to write in the batch file because I am a bit new to 10g ?
Thank you very much

>
How to make a scheduled shutdown immediate and full database export ? I want to use a batch file for it so I can make a sheduled task from the windows control panel everyday at 2 am. So what to write in the batch file because I am a bit new to 10g ?No, you can't take logical backup after shutdown database.
If you want to schedule the logical backup of your database, just you can refer from here
Schema level
http://mohamedazar.wordpress.com/2010/04/18/datapump-scheduler-for-schema-level/
Full export
http://mohamedazar.wordpress.com/2010/02/16/dbms-scheduler-for-data-pump/

If shutdown immediate hangs database waits one hour for shutdown abort

we have schedules cold backup for our 11g database on redhat 5.3.
there is a shell script written with shutdown immediate command.
If database hangs during shutdown immediate database waits one hour for auto shutdown abort.
but this happens once or twice in a month
can we do this auto shutdown abort earlier than one hour ??

user13376823 wrote:
we have schedules cold backup for our 11g database on redhat 5.3.
Since you're shutting down the database for cold backup so ensure it should be shutdown properly by shutdown or shutdown immediate cmd not by abort cmd.
Consistent backup:-
A backup taken when the database is mounted (but not open) after a normal shutdown. The checkpoint SCNs in the datafile headers match the header information in the control file. None of the datafiles has changes beyond its checkpoint. Consistent backups can be restored without recovery.
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1007616

Shutdown immediate hangs and HVM of a database

Hi,
I have following questions,
1. What are the possible causes of SHUTDOWN IMMEDIATE command hangs
and doesnt responds.
2. What do u mean by High Water Mark(HVM) of a database. Because when we
give SHUTDOWN IMMEDIATE command there is message in alert log file
mentioning the HVM of a database.
3.Also is there any relationship between shutdown process taking long time to
shutdown a database and HVM of a database.
4. If the database instance is up for a long time then does it take long time to
shutdown a instance.
Thanks,
Girish A

Hello,
for 1.) view Metalink Note:375935.1. Maybe you even get an error: "SHUTDOWN: Waiting for active calls to complete". This has nothing to do with HWM but with already logged on sessions. Immediate means new connections are not able to log in, existing connetions are not disconnected at once.
for 2.) the HWM is the highest point to which datafiles have been filled up. This is the value to which you are able to shrink (if you desire to). View Metalink Note:1034330.6 for message "License high water mark" in alert.log at shutdown ("highest number of concurrent users sessions").
Greets,
Hannibal

Is it safe to control c out of a shutdown immediate?

development database
10.1.0.3
solaris
I did a shutdown immediate and it is taking time to shut down. something is probably running. I should have checked first and could n ot. I tried sqlplus / as sysdba to create another session and 10.1.0.3 is too old to do that while shutting down.,
is it safe to control c out of this shutdown
shutdown abort
startup
shutdowm immediate
startup
or might I corrupt the database?
I need to bounce this irregardless of what is running.

Hi Anantha,
slight correction: uncommitted transactions are not rolled back during the shutdown abort. But they are rolled back during the next startup of the instance during the crash recovery phase. So at the end, the database looks exactly the same as after a shutdown immediate-startup sequence. That is, if you have all the online logfiles in place needed for the crash recovery.
Kind regards
Uwe

Mail gave error message, failure to move e-mail to trash can. Mail has frozen and will not quit and is stopping a machine shutdown. Problem persisted even after power was trend off for a minute.

Mail gave error message, failure to move e-mail to trash can. Mail has frozen and will not quit and is stopping a machine shutdown. Problem persisted even after power was trend off for a minute.Iideas please

OS X: How to quit an unresponsive application using Force Quit
Back up all data. Rebuild the mailbox. Try to delete the message again.

Shutdown immediate problem

Similar Messages

Maybe you are looking for