Asap.Ksh Sample Script Affects Performance Significantly (Doc ID 948224.1)

Last updated on MARCH 09, 2011

Applies to:

Oracle Communications ASAP - Version: 5.2.4 and later   [Release: 5.2 and later ]
Information in this document applies to any platform.

Goal

The ASAP.ksh script used by Veritas to monitor ASAP executes multiple times when it could make a single call and parse the output. For example:

function monitor_java_pid
{
let found=0
jids=`cat ${ASAP_BASE}/.asap.java.pids | $GREP $1 | $AWK '{print $1} '`
if [ ${#jids} -gt 0 ]
then
for i in ${jids}
do
id=`$PS | $GREP -v VRTSvcs | $GREP -v ASAP.ksh | $GREP ${OWNER} | $GREP -v PID | grep ${i} |
$AWK ' { print $2} '`
if [ ${#id} -eq 0 ]
then
continue
fi
let found=1
echo "\t\t---- ASAP java process ${id} running for : ${1} ----"
done
else
return 0
fi
if [ ${found} != 0 ]
then
return 0
else
return 1
fi
}

When the cluster scripts are running CPU usage is 40%+ - performance of all monitoring scripts need to be enhanced.

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms