What are saf_epiPoz files, how can I remove them?

Products

• DIRECTORY
• CA IT Asset Manager
• CA Software Asset Manager (CA SAM)
• ASSET PORTFOLIO MGMT- SERVER
• CA Service Management - Service Desk Manager
• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• CA Workload Automation Agent
• CA Process Automation Base

Issue/Introduction

What are saf_epiPoz files, how can I remove them?

saf_epiPoz.xxx are store and forward files which are iGateway process for embeddedapplications writing events to logdepot in EEM. This document shows you how to reduce the files in your environment.

 

Environment

Release: ETRIA199000-8.4-Embedded Entitlements Manager
Component:

Resolution

saf_epiPoz.xxx are store and forward files which are iGateway process for embeddedapplications writing events to logdepot in EEM.

These saf_epi type files will build up when there was an EEM processing error. The saf_epi files WILL grow steadily but normally do not exceed 8Mb in size - also there should only be 1 set of files(the idx_ and saf_) which will be actively processed.

Events in the saf files are written to logdepotdb file in the iTechnology directory.

To reduce the amount of files being generated please do the following:

On Windows

1. Go to the EEM Server with the files:
2. Stop the iGateway Service (go to Start run, type services.msc, find the iGateway server and right click and stop the service)
3. Open up windows explorer
4. Go to %IGW_LOC% home directory, and remove the lowest "saf_epiPoz.xxx" file with the corresponding "idx_epiPoz.xxx" file.
5. Restart the iGateway Service, and the reporting should start working properly.

On Linux

1. $IGW_LOC$./S99gateway stop/
2. cd $IGW_LOC$
3. remove the lowest "saf_epiPoz.xxx" files with the corresponding "idx_epiPoz.xxx" file. Keep the most recent one.
4. Restart the iGateway Service
5. $IGW_LOC$./S99gateway start

Also please be advice that the CAELM reporting has been removed from the EEM r12 releases, and fixes for CAELM in the EEM 8.4 will not be followed through.