ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

UIM Oracle probe max_restarts and windows event Faulting module name: KERNELBASE.dll

book

Article ID: 186943

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After restarting Oracle probe, it turned red and log shows Max restarts.
When we look at windows event viewer we see this error

Faulting application name: oracle_monitor.exe, version: 0.0.0.0, time stamp: 0x5e54b7f9
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19425, time stamp: 0x5d26b6e9
Exception code: 0xc0000005
Fault offset: 0x000000000000908c
Faulting process id: 0xea4
Faulting application start time: 0x01d5fe1490b567a3
Faulting application path: E:\Program Files (x86)\Nimsoft\probes\database\oracle\oracle_monitor.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: d04d2b0a-6a07-11ea-8126-0050569737c0
Faulting package full name:
Faulting package-relative application ID:

Cause

After reviewing the oracle_monitor.cfg file.
We found a started profile that was never completed.

<server_1234>
   suspended = no
   active = yes
   interval = 
   heartbeat = 
   p_timeout = 
   sql_timeout = 
   set_alarm_source_as_qos_source = 0
</server_1234>
 
 a normal profile looks like this:

<server_2222>
      active = yes
      description = server_2222
      connection = server_2222
      interval = 5 min
      heartbeat = 5 sec
      p_timeout = 15 min
      sql_timeout = 30 sec
      p_tout_msg = p_timeout_1
      sql_tout_msg = sql_timeout_1
      tout_clear = timeout_clear_1
      p_tout_sev = major
      alarm_source = server_2222.broadcom.com
      group = 
      set_alarm_source_as_qos_source = 0
      suspended = no
      con_fail_msg = connect_failed_1
   </server_2222>

Environment

Release : any Windows version of UIM 

Component : UIM - ORACLE

Resolution

Delete the incomplete profile and restart the robot as the probe in the error state may not restart cleanly.