SARM Files Cannot Be Processed Using Sarmuery (Doc ID 2195962.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version 8.1.1.14.6 [IP2014] and later
Information in this document applies to any platform.

Symptoms

SARM files cannot be processed using sarmquery utility.

Setup SARM with the following settings :

change param SARMMaxFiles=5 for comp FINSObjMgr_nld
change param SARMThreshold=100 for comp FINSObjMgr_nld
change param SARMPeriod=1 for comp FINSObjMgr_nld
change param SARMLevel=1 for comp FINSObjMgr_nld

SARM files are created in log directory, but not able to process them using sarmquery. Able to use sarmanalyzer.

sarmquery output:

sarmquery -i A_FINSObjMgr_nld_T201609222247_P9830402_N0025.sarm -output debug=stderr
###################################################
sarmquery
  General Flags:
  Filters:
  Aggregations:
  Output: debug=stderr,txt
  Number of Input Files: 1
Collecting 1 input files...

Analyzing input files...
  elapsed time : 00:00:00 : 0% data processed

Not a SARM File: /appl/sba81/siebsrvr/enterprises/Siebel/uaix1016/log/A_FINSObjMgr_nld_T201609222247_P9830402_N0025.sarm (file offset 12787136)
Unable to collect headers
Ignoring invalid file '/appl/sba81/siebsrvr/enterprises/Siebel/uaix1016/log/A_FINSObjMgr_nld_T201609222247_P9830402_N0025.sarm'


** Plan Generation Error **

No valid sarm files were found
  # Invalid or non-sarm files : 1
  # Empty sarm files : 0
(use '-output debug=stderr' for details)
Try 'sarmquery -help'

*** sarmquery exited with ERROR 1 ***
###################################################

According to Doc ID 2164193.1, SARMThreshold must set the threshold to 0 for sarmquery to work. This works in their PAT environment, but is not an acceptable solution for production.
They would like another solution so they can use sarmquery with the SARM file amd threshold=100 switched on.

Reason: If SARMthreshold is set to 0, lot of files and data are generated in production environment, that impacts performance of the UNIX Siebel server.
As 98.5% of the transactions are within 100 ms, this is not interesting from a performance point of view. By changing this setting to 100, less files are generated and only information that is relevant for customer's performance monitoring.

Cause

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