getting oracle probe alarms from a robot that had the oracle probe removed, why?

book

Article ID: 193692

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

Getting oracle probe alarms from a robot that had the oracle probe removed, why?

hostname||14808659||Profile
HOSTNAME(10.1.1.10)-SID, instance SID, cannot connect to database:
(Create OCI environment failed with rc = -1)

oracle monitor probe version 5.45

Cause

- leftover oracle_monitor process

Environment

Release : 9.2.0

Component : UIM - ORACLE

Resolution

1- Stop Nimsoft service on the bad robot

systemctl stop nimbus

2- Stop /kill  any processes from Nimsoft.

ps aux | grep nimbus

3- Delete the /opt/nimsoft/probes/ < oracle backup folders >

4- Backup, then delete these files

/opt/nimsoft/robot/q1.rdb 

/opt/nimsoft/robot/q2.rdb files

5- Start the nimsoft robot watcher service

systemctl start nimbus

If that doesn't work, check to see if there is an oracle_monitor.exe leftover on the client/Robot machine where the probe used to be installed. Kill that process.

Then deactivate the robot watcher service, and do the following:

- delete the robot niscache folder
- delete the robot.sds file
- Acknowledge all of the false alarms
- Activate the robot

If all of the above doesnt work, reboot the machine.

In this case, there was a leftover oracle_monitor.exe/oracle_monitor process.