shutdown but still got oracle processes

[yls177]

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?

[davey23uk]

you didnt actually shut it down, lets see what you typed and variables and such like

[edsperez]

You can try shutting down the database again, then kill the othe oracle process manually, then you can start your db.

[Dilippatel]

Can you paste output of the command

ps -ef | grep ora

[padawin]

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.

[ckwan]

I guess your listener service is still alive.

[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

[yls177]

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

[adewri]

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...

[yls177]

Originally posted by adewri
.............
4. When you need to .......................

Contd. on the last page... [/B]

where is the last page?