shutdown but still got oracle processes

[yls177]

hi, below are my steps

1) shutdown immediate;
2) but oracle still hanging, as in can do a ps -ef | grep ora and still the set of family oracle processes are alive
3) so i do a select * from v$instance;
4) and when it says that " oracle not available"
5) then i safely do a shutdown abort
6) finally, the family set of oracle processes are gone.

but is it absolutely safe to do this?

please confirm

[KenEwald]

If it's the only database running on that machine, run ipcs to see if the Shared Memory Segments and Semaphore Arrays are still alive. It's rare, but some times they don't die if you've had an abnormal database abortion.

ipcrm will remove them (check man pages for syntax). This WILL definately shut your database down. It's as effective as a power switch on a unix/linux operating system.

Best of luck.

shutdown abort is a last resort and ipcrm is a final and fatal resort.

You shouldn't have any trouble bring the database back up. It'll do a delayed recovery on it's own when it comes back up.

[yls177]

in my alert file, i had the following entries.


Thu Nov 20 22:05:29 2003
Shutting down instance (immediate)
License high water mark = 122
Thu Nov 20 22:08:06 2003
Shutting down instance (abort)
License high water mark = 122
Instance terminated by USER, pid = 115688


Thu Nov 20 22:08:16 2003
alter database open
Beginning crash recovery of 1 threads
Thu Nov 20 22:08:17 2003
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 1 Seq 244585 Reading mem 0
Mem# 0 errs 0: /oracle/SID/origlogA/log_g15m1.dbf
Mem# 1 errs 0: /oracle/SID/mirrlogA/log_g15m2.dbf
Thu Nov 20 22:08:17 2003
Thread recovery: finish rolling forward thread 1
Thread recovery: 3 data blocks read, 3 data blocks written, 2 redo blocks read
Crash recovery completed successfully


my questions
1) both shutdown statements (one is immediate, the other is abort). does that mean that there are 2 shutdown statements, one is shutdown immediate, and the other is shutdown abort.

2) also, oracle did recovered the database successfully?

thanks

[KenEwald]

Looks like you did a shutdown immediate, then abort, then started up.

It also looks like the startup recovery was good.

[yls177]

okay.. i guess i am fortunate this time. cos i think shutdown abort will gives some database big headaches like inconsistency, database cant startup and etc.. am i right

[davey23uk]

shutdown abort isn't a bad thing, only in rare cases will a shutdown abort give you problems where you lose an online redo log.

Normally Oracle is very good at recovering itself from that so dont worry too much if you have to do one

[yls177]

i am quite a cautious guy.... so wont try dangerous stuffs... i am concerned cos my colleagues kept doing shutdown abort when immediate takes a while....


i told them things like rollback, switch logfile and etc./..

[pando]

we do shutdown abort all the time

part of backup process when taking cold backups

[rajabalachandra]

hi pando,

do you take the cold backup just after a shutdown abort.

is it OK.


Raja

[pando]

we do

alter system switch logfile
alter system checkpint
shutdowna bort
startup restrict
shutdown immediate