Performance Issue Caused By 0 Byte AGProc.Log And ESMPROC.Log Files On Argus Transactional Server (Doc ID 1629800.1)

Last updated on JANUARY 15, 2016

Applies to:

Oracle Argus Interchange - Version 7.0.2 and later
Information in this document applies to any platform.

Goal

Argus Safety and Argus Interchange Services are creating lot of of 0 byte AGProc.log, ESMPROC log, E2bReceive.log, Esmmapping.log and interchangeservice.log  files in C:\Temp\ArgusLogs\Argus and C:\Temp\ArgusLogs\Interchange folders. These files are causing performance issue on the Argus Transactional Server.
 

Example File name for o byte AGproc.log file:
  - AGProc.AGProc.D[2014-04-16].T[22-03-00].P[03300].log

Example File name for o byte esmproc.log file:
  - ESMProc.esmproc.D[2014-04-29].T[11-55-06].P[02236].log

Example File name for o byte e2Breceive.log file:
  - E2BReceive.E2BReceive.D[2014-04-29].T[12-01-44].P[02032].log

Example File name for o byte esmmapping.log file:
  - ESMMapping.ESMMapping.D[2014-04-29].T[11-46-55].P[03656].log

Example File name for o byte Interchangeservice.log files:
  - InterchangeService.InterchangeService.D[2014-04-29].T[11-54-53].P[04092].log

 

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