SARM Files Are Getting Generated With Zero (0) Bytes When Setting A Shared Drive Location On SARMLogDirectory Parameter (Doc ID 2985351.1)

Last updated on NOVEMBER 07, 2023

Applies to:

Symptoms

SARM has been enabled for a custom component named BMORetailMQRcvr and for FINSObjMgr_enu object manager component, but the generated .SARM files have 0 (zero) bytes.

Below are the parameters set at the Siebel Server component level:

PA_ALIAS                  PA_VALUE
-----------------------  -------------------------
SARMBufferSize         5000000
SARMClientLevel        0
SARMFileSize             15000000
SARMLogDirectory      \\optz\Q6_sarm
SARMMaxFiles            4
SARMPeriod               3
SARMThreshold          0
SARMUsers
SARMLevel                2
SARMEnabled            True
SARMMaxMemory      4000000


The issue can be reproduced at will with the following steps:

1. Login to srvrmgr
2. Set the SARM parameters as listed above at the server component level for the desired component
3. Submit some load to the component
4. The .SARM log files are getting generated with 0 (zero) bytes on the specified SARM log directory

Changes

N/A 

Cause

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