shutdown but still got oracle processes
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: shutdown but still got oracle processes

  1. #1
    Join Date
    Oct 2002
    Posts
    391

    shutdown but still got oracle processes

    hi, in svrmgrl, i did a shutdown, the system replied that the database is shutdown. however, i did a ps -ef | grep ora, and i still find these oracle processes. afterwhich i did a startup, and the system told me that oracle is still running. what is wrong?

  2. #2
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    you didnt actually shut it down, lets see what you typed and variables and such like

  3. #3
    Join Date
    Jan 2001
    Location
    St. Louis. MO
    Posts
    150
    You can try shutting down the database again, then kill the othe oracle process manually, then you can start your db.

  4. #4
    Join Date
    Feb 2003
    Location
    INDIA
    Posts
    96
    Can you paste output of the command

    ps -ef | grep ora
    Dilip Patel
    OCP 8i

    Catch me online at Yahoo: ddpatel256

  5. #5
    Join Date
    Jun 2003
    Posts
    22
    Do you have multiple databases on the system? If so, did you set the ORACLE_SID to shutdown the appropriate database? The SID name is appended to oracle processes.

  6. #6
    Join Date
    Oct 2000
    Posts
    250
    I guess your listener service is still alive.

  7. #7
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    In a normal shutdown, oracle will wait untill all the connections are closed and then only it will shutdown.

    You might want to issue shutdown immediate/shutdown abort


    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


  8. #8
    Join Date
    Oct 2002
    Posts
    391
    Can you paste output of the command

    ps -ef | grep ora
    i wished i could. but now the database is okay and running. anyway, the output of ps -ef | grep ora is the oracle processes with smon, pmon, archiver, lgwr, dbwr and etc.......


    Originally posted by sambavan
    In a normal shutdown, oracle will wait untill all the connections are closed and then only it will shutdown.

    You might want to issue shutdown immediate/shutdown abort


    Sam
    this is what actually happens
    1) we had scripts to shutdown/startup the database for offline backup in our crontab entries
    2) and these scripts had been working fine.
    3) but recently, there had been 2 times when the scripts are not working
    4) scenario: couldnt startup database therefore go and analyze
    5) found that the shutdown script did not shutdown the database. Cos going into svrmgrl, and doing a startup says that "the oracle instance is still running"
    5.1) do a ps -ef | grep ora and indeed saw all these oracle processes including the shutdown script entry.
    5.2) going back to svrmgrl, did a shutdown immediate. still same result in 5.1
    5.3) colleague did a shutdown abort and it works.

    my questions

    1)is that isnt it dangerous to do a shutdown abort. actually, i was thinking about killing all the orace processes. so which is more advisable?

    2) what are the valid reasons doing a shutdown abort.

    thanks

  9. #9
    Join Date
    Nov 2002
    Location
    New Delhi, INDIA
    Posts
    1,796
    Originally posted by yls177
    my questions

    1)is that isnt it dangerous to do a shutdown abort. actually, i was thinking about killing all the orace processes. so which is more advisable?
    Shutdown abort and killing the background process are same and both are not advisable.

    Originally posted by yls177

    2) what are the valid reasons doing a shutdown abort.

    thanks
    Sometimes it happens that when long batch processes or long transactions are running and you want to take backups and do a shutdown immediate then it might take hours for a shutdown or even look as if there is no response. Then you can possible do a shutdown abort. But be mentally prepared for unexpected results . And yes after a shutdown abort do not forget to startup and do a shutdown immediate again before taking the backup.

    Other reasons can be....

    1. When the building is on fire and you need to run .
    2. When you need to show the developers who is in control.
    3. When you want to act coooool and show off that you can recover from a shutdown abort.
    4. When you need to .......................

    Contd. on the last page...
    Amar
    "There is a difference between knowing the path and walking the path."

    Amar's Blog  Get Firefox!

  10. #10
    Join Date
    Oct 2002
    Posts
    391
    Originally posted by adewri
    .............
    4. When you need to .......................

    Contd. on the last page... [/B]
    where is the last page?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width