Oracle shutdown immediate;

[Edgar Brito]

I execute these commands to shutdown the instance. Oracle Database 10g Enterprise Edition Release 10.2.0.4.0

1) #sqlplus
2) Enter user-name: / as sysdba
3)SQL> shutdown immediate;
4)Oracle process turns to defunct

#ps -efa |grep 24969
oracle 25039 24947 0 20:42:30 pts/2 0:00 grep 24969
oracle 24969 24968 1 20:37:58 ? 0:00

5) LOG umsnh_ora_24979.trc registers these messages

killed 0 out of 1 processes.
Starting kill, force = 0
Attempt 37 to re-kill process OS PID=24969.
killed 1 out of 1 processes.
Starting kill, force = 0
killed 0 out of 1 processes.
Starting kill, force = 0
killed 0 out of 1 processes.
Starting kill, force = 0
Attempt 38 to re-kill process OS PID=24969.

Why Oracle process is defunct?
How to fix it?

[Steven E. Protter]

Shalom,

Was the oracle process defunct before the shutdown?

Either way there are two areas of investigation.

New or missing OS patches from HP concerning process management.

Oracle patches dealing with system behavior in a shutdown immediate.

Suggest a visit to http://metalink.oracle.com as a start.

SEP

[Frank de Vries]

Oracle works in TWO TASK ,
thus you have oracle process and shadow process (or client process).

This is happening in PGA. If client process does an invalid operation it can become detached from its oracle process and causes a defunct.

Try to identify which application was attached to it ..

[Edgar Brito]

The Oracle process was not defunct

(1) oracle 4579 4396 0 09:34:09 pts/1 0:00 sqlplus
(2) oracle 4580 4579 0 09:34:12 ? 0:00 oracleUMSNH
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
(3) oracle 4580 4579 0 09:34:12 ? 0:00

The defunct process is 2 and 3 (diferent timestamp) the parent

was a sqlplus session
*************************+

2. And what happens if they try to kill the parent manually?
*************************+
shutdowns normally
*************************+

[Frank de Vries]

Edgar,

The ps -ef you are showing is typical.
The client process and oracle process become detached (of course this is not normal behaviour) in such a way that the process table of unix cannot update its adminstration.

The process is there but its relation is foobar

When doing a shutdown immediate does not work,
then open a new sqplus session and do a
shutdown abort