topic Re: Background processes still active after shutdown immediate in Operating System - HP-UX

Background processes still active after shutdown immediate

Roberto Martinez_6 — Thu, 02 Oct 2003 07:49:38 GMT

Hi, in our new 9.2.0 database installation, after issuing a "shutdown immediate" command, it returns ok with the regular oracle database shutdown message, but after a "ps -ef | grep ora_", the ora_* processes are still there (pmon, smon, ...).
Have you ever had this behaviour?
TIA.

Re: Background processes still active after shutdown immediate

Pete Randall — Thu, 02 Oct 2003 08:03:07 GMT

Do your Oracle shutdown scripts provide for shutting down these processes? Eventually the O/S shutdown will reach the point where it will kill everything, but your scripts should handle the graceful shutdown of all your Oracle process.

Pete

Re: Background processes still active after shutdown immediate

Roberto Martinez_6 — Thu, 02 Oct 2003 08:07:19 GMT

In fact, I'm still testing so there's no startup/shutdown script, but a telnet connection plus the standard commands:

$ sqlplus /nolog
SQL> connect sys/change_on_install as sysdba
SQL> shutdown immediate
...
SQL> exit

, then I wait several minutes, issue a ps -ef | grep ora_ , and there are they!.

It's the only instance running 9.2 on the machine (I've another 8.1.7 running), and I've double-checked ORACLE_SID and ORACLE_HOME before...

Re: Background processes still active after shutdown immediate

Yogeeraj_1 — Thu, 02 Oct 2003 08:15:28 GMT

hi,
*
check for all messages in any trace file (background and user) as well as the alert.log
*
what's in there?
*
Revert
Yogeeraj

Re: Background processes still active after shutdown immediate

Hari Kumar — Thu, 02 Oct 2003 08:18:57 GMT

Very interesting....
Can you please give the messages of alert log file of your instance ??
Does this kind of messages appear after shutdown command -------
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 2
Thu Oct 02 18:46:56 2003
ALTER DATABASE CLOSE NORMAL

Re: Background processes still active after shutdown immediate

twang — Thu, 02 Oct 2003 08:26:14 GMT

I would suggest you to monitor the message in alert logfile, you may,
1. open a telnet session and issue the following command:
$ tail -f alertSID.log
2. open another telnet session, and issue the shutdown command:
$ sqlplus /nolog
SQL> connect sys/change_on_install
SQL> shutdown immediate;

Do you see the shutdown message shown in the logfile or any other further message appears such as startup message right after the database shutdown?

Re: Background processes still active after shutdown immediate

Roberto Martinez_6 — Thu, 02 Oct 2003 08:28:48 GMT

Funny, I'm trying to reproduce behaviour to check alert files, but now it works as it should. Apparently the wrong behaviour happens after several hours (maybe 1 day) of inactivity. I'll check everything tomorrow and update this thread. Thanks all and keep online...

Re: Background processes still active after shutdown immediate

Hari Kumar — Thu, 02 Oct 2003 08:33:44 GMT

Can you please let us know from your alert log, that any kind of these messages
'Waiting for active calls to complete'
and also please do update us with your alert log messages, which would be a great help to us in learning a new scenario........

Thanks,

Re: Background processes still active after shutdown immediate

Roberto Martinez_6 — Fri, 03 Oct 2003 02:14:07 GMT

Well, apparently my db wants to play with me... The problem is not being reproduced. Anyway, I'll install the last patchset. Thank you all very much and excuse me for taking your valuable time.

Re: Background processes still active after shutdown immediate

Duncan Edmonstone — Fri, 03 Oct 2003 03:27:20 GMT

Your not running MC/ServiveGuard or any other monitoring software are you?

It's common practice in ServiceGuard to set up a database monitor which restarts an Oracle instance if it stops... On my MCSG systems I have on occasion had new/inexperienced DBAs come and tell me 'hey I shut down oracle to do some maintenance and now its running again!'

HTH

Duncan