Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

SHR Availability shows less hours. How to recollect the data for last day and re-aggregate

SHR Uptime report shows less hours. we have verified and data is available on agent.

How can I re-collect past 2 days data and re-aggregate the availability report.?



Labels (2)
2 Replies
Micro Focus Expert
Micro Focus Expert

Hello Rupesh,

The answer is different depending on what version of SHR or OBR you are using within your environment and if you are using OA.

By default, OBR will collect 15 days of history information.

There are two steps to take assuming that your data is being processed properly.

  • Increase the amount of history being collected by the OBR Collector from OA
  • Run the aggregate process after the data is collected and within the DB.

Here are two knowledge articles that should help you with this process.

KM00707880 - Service Health Reporter (SHR): How to aggregate late arriving samples.

KM03287475 - How to collect more historical data from Operations Agent (OA) within Operations Bridge Reporter (OBR) 10.30 or later?

I hope that this information is helpful.



Mark Butler
Micro Focus SW Support Engineer
Micro Focus Contributor
Micro Focus Contributor

Hi RupeshKashavan
with the post you are not specified the Application version.
In general OBR will collect last 15 days data when you add a new data source to the application ( initial history collection) and later OBR application will use an internal mechanism to collect the data from the last collection point during its next collection. OBR internally restricts the time difference between the last collection point and the current collection time again 15 days . i.e. if this difference is more than 15 days (360 hours) OBR will collect only he last 15 days data.
So with a production system the above scenario is not usual as OBR is configured to collect data from the source every hour. following scenarios can occur
1) there are some network issues and node is not reachable from the collection station
data will get collected from the last collection point, if the network issue is getting addressed within 15 days timeframe
2) Communication issues between OBR and the collector prevent data processing from a collector
All the piled-up data will be getting processed once you have addressed the communication/ certificate issues between the OBR and Collector system
3) late arrival data is not getting aggregated to the aggregate table
This scenario is gracefully addressed with 10.40 version hence if you are in lower version of OBR please upgrade to 10.40 that will prevent such issues going forward.
currently you have to re-aggregate the data as lower versions the data processing using abcStreams will consider last two days data to the higher tables.
you can use the below commands to do it for availability pattern
perl %pmdb_home%\scripts\aggregate\SR_SM_NODE_AVAIL_SH_SM_NODE_AVAIL_HourlyNodeAvailability.ovpl -lagtime 30 –f
perl %pmdb_home%\scripts\aggregate\SH_SM_NODE_AVAIL_SD_SM_NODE_AVAIL_DailyNodeAvailability.ovpl -lagtime 30 –f


Still you are using SHR  (SHR 9.4x)  please  migrate to OBR as SHR  is an EOL state.




The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.