Database Tuning (MOSC)

MOSC Banner

oswatcher defunct processes

edited May 19, 2017 5:03AM in Database Tuning (MOSC) 6 commentsAnswered

Using the latest, OSWatcher (734), have noted its processes become defunct processes.  No impact, but curious what is happening.

The actual data collection processes that OSWatcher calls are becoming defunct after they run...

eg.

(1) ps checking main oswatcher PID:

sdb0212v02:NDSP2:/opt/app/oracle/admin#ps -fe | grep 22189 | grep -v grep

  oracle 15669 22189 0 07:59:06 ? 0:00 sleep 20

oracle 15660 22189 0 07:59:06 ? 0:00 /bin/sh ./iosub.sh /opt/app/oracle/admin/oswbb/archive/oswiostat/ssdb0212v02_io

  oracle 15656 22189 0 - ? 0:00 <defunct>

  oracle 23908 22189 0 09:30:30 ? 1:27 /bin/sh ./OSWatcherFM.sh 48 /opt/app/oracle/admin/oswbb/archive

oracle 15664 22189 0 07:59:06 ? 0:00 /bin/sh ./xtop.sh /opt/app/oracle/admin/oswbb/archive/oswtop/ssdb0212v02_top_17

  oracle 15668 22189 0 - ? 0:00 <defunct>

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center