My Oracle Support Banner

AG Services Status Field Is Not Populated (Doc ID 1488015.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Argus Safety - Version 7.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 23-Jul-2014***
***Checked for relevance on 16-Aug-2017***
***Checked for relevance on 12-Apr-2019***

Symptoms

After upgrading to Argus 7.0.1 and using Database 11.2.0.3, the status field for all all AG Services in AG Service configuration window or agservice.ini is not populated.
The AG service log file is either started or timed out, however no additional errors are being captured.

ie.

Bulk Report Print > "D:\..\Argus Safety\AGProc.exe Bulk Report Print Bulk Report Print" started.
Report Scheduling > "D:\...\Argus Safety\AGProc.exe Report Scheduling Report Scheduling" timed out.
General Email > "D:\....\Argus Safety\AGProc.exe General Email General Email" timed out.
Scheduling Check > "D:\...\Argus Safety\AGProc.exe Scheduling Check Scheduling Check" started.
Report Scheduling > "D:\...\Argus Safety\AGProc.exe Report Scheduling Report Scheduling" started.
General Email > "D:\...\Argus Safety\AGProc.exe General Email General Email" started.

  

The alert.log file is capturing messages similar to the following:

ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB"
ORA-04063: package body "DBSNMP.BSLN" has errors
ORA-06508: PL/SQL: could not find program unit being called: "DBSNMP.BSLN"
ORA-06512: at "DBSNMP.BSLN_INTERNAL", line 2073
ORA-06512: at line 1

  

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.