Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
echo $ORACLE_SID
YBRD
conn sys/hello as sysdba
SQL>shutdown immediate

Then I was waiting for it to shutdown for a couple of minutes. It didn't, so I closed my window.

Then I again logged in and it displayed:

ORACLE IMMEDIATE SHUTDOWN IN PROGRESS

Will it shutdown automatically by itself after a while?

share|improve this question
add comment

migrated from stackoverflow.com May 9 '13 at 7:02

This question came from our site for professional and enthusiast programmers.

3 Answers

Yes, it will -- of course if it persistently refuses to you might have to kill the processes, and face instance recovery on restart.

share|improve this answer
add comment

Normally it should happen quickly. There could be large transactions that take a while to rollback, or a long running transaction that takes ages to end.

If the time is spent for the rollback, you could crash the instance with a good and solid kill -9 on the server procs and use parallel instance recovery. Normally this should not happen but parallel instance recovery can be quicker than a recovery by 1 process.

see Oracle manual

share|improve this answer
add comment

According to "Shutdown Timeout" section in Database Administrator's Guide, shutting down the database in any of the following modes may take up to one hour:

  • Normal Mode

  • Immediate Mode

  • Transactional Mode

Shutdown in Abort Mode will bring your instance down in a short amount of time not allowing it to checkpoint (see "Overview of Checkpoints" in Database Concepts), and the next time it's started the crash recovery will be automatically performed which may take some amount of time.

Sometimes Transactional Mode shutdown may be faster than the shutdown with Immediate Mode since Immediate Mode shutdown rolls back all transactions that were running when the shutdown was initiated, and if some DML had already updated millions of rows, committing it would be faster than rolling it back, because most of the changes are already in the redo log and in data files.

share|improve this answer
    
@Mat Okay, I will not believe blindly in the documents anymore. I will not believe blindly in the documents anymore. I will not believe blindly in the documents anymore. I will not believe blindly in the documents anymore... (: –  Yasir Arsanukaev May 23 '13 at 15:26
    
@Mat I need to test it to improve the answer, or you can edit it, because you have more experience (: –  Yasir Arsanukaev May 23 '13 at 15:37
    
Actually I'm having doubts about the immediate case... seems like it should timeout too (really hard to test though :-)). Replace "may take up to an hour" by "may timeout after an hour" and your answer should be correct. (After a shutdown timeout the database isn't shut down.) –  Mat May 23 '13 at 15:43
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.