./AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.cmd|../AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.sh|"../artools/arexport.sh"|"./artools/arexport.bat"|"pdp.sh"|"./artools/pdp.bat"|"remoteaction/remoteaction.sh"|"remoteaction\remoteaction.bat"|"DMLDataImport.bat"|"DMLDataImport.sh"|"/opt/bmc/ARSystem/db/mkdir.sh"

However, the first command is rundashboardutil.cmd and it doesn't have double-quotes.  All other values in the whitelist parameter contain double-quotes.
The string has to be corrected and then the whitelist will accept and run the rundashboardutil.cmd.

In the solution for the test use-case, the issue is in a container, the following change was made to the Run-Process-Command-Whitelist parameter:

"/opt/bmc/AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.sh"|"../artools/arexport.sh"|"./artools/arexport.bat"|"pdp.sh"|"./artools/pdp.bat"|"remoteaction/remoteaction.sh"|"remoteaction\remoteaction.bat"|"DMLDataImport.bat"|"DMLDataImport.sh"|"/opt/bmc/ARSystem/db/mkdir.sh"

Note that after applying Solution 4, it was found that Solution 3 above was also necessary.  Once Solutions 3 and 4 were performed, the Dashboard utility would run daily as expected.

If the above steps do not resolve the issue then as an additional Step you can run the rundashboardutil.cmd utility from the Command prompt and check if it gets triggered.

In one of the use case we could see the below Error:



In order to resolve this Error extract the dashboarddatagenerator-9.1.10-SNAPSHOT jar and check if DashboardDataGenerator file is present under com/bmc/cmdb/ui/dashboard folder.

If it is missing replace it from the other working environment.

• Applications> AR System Management Console> AR System Server Group Console
• On left side select Current Operation Owner

4. Click on the Home Page Flyout menu Applications > AR System Administration Console > System > General > Centralized Configuration. Choose Component Type: com.bmc.arsys.server.shared > *
Make sure Disable-Escalations-Global is set to "F" 





5. Run again the rundashboardutil.sh or rundashboardutil.cmd command and validate the "CMDB:Dashboard_ScheduleManager" form.

Cause 6: Java heap memory in KPI or Datasource dashboard

Solution 6: 
The logs can be found in the ARSystem/db path based on the installation path and on the server wherever escalation is ranked 1
DashboardDataGenerator_DATASOURCES_xxx.log
DashboardDataGenerator_KPI_xx.log

Sample errors details
[ java.util.concurrent.ExecutionException ] Thread - 40 : Could not get restuls from CI Completeness processors: java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space

 java.util.concurrent.ExecutionException ] Thread: 57 Error while waiting main reader to complete for class BMC.CORE:BMC_Product: java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space

For this in  rundashboardutil.cmd or rundashboardutil.sh (in case of Linux  environment) file udpate the memory parameter.
DASHBOARD_UTIL_JAVA_OPTIONS=-Xmx1536m
to 
DASHBOARD_UTIL_JAVA_OPTIONS="-Xms512m -Xmx4096m"
The file has to be placed in the server. /opt/bmc/AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.sh (linux)
Restart all platform servers

Cause 7: Performance issue with huge CI data.

<TrID:                               > Thread: 53 Completed processing class BMC_STORAGESUBSYSTEM Found 0 [10 Jun 2024 21:05:51,833] [ERROR] :  <TrID:                               >  [ com.bmc.arsys.api.ARException ] Thread - 40 : Could not fetch total number of instances for class BMC.CORE:BMC_BaseRelationship in BMC.ASSET dataset: ERROR (552): The SQL database operation failed.; terminating connection due to administrator command

  <TrID:                               >  [ com.bmc.arsys.api.ARException ] Thread - 18 : Could not update heart beat field: ERROR (552): The SQL database operation failed.; 

Solution 7: 

As a workaround, we excluded BMC_PRODUCT class from completeness KPI run as it had multiple errors
in DashboardDataGenerator_KPI log

A defect is logged DRD21-102929 to check the performance issue.

How to fetch Dashboard logs for review:
--Goto ITSM Homepage->Expand Application->AR System Server Group Console
-->Go to Logs->View Logs
->>Now select FTS0 server -->Check for logs having latest runid after keyword DashboardDataGenerator_DATASOURCES and DashboardDataGenerator_DATASOURCES_KPI.
>>You can get current utility run job id from form CMDB:Dashboard_Utility_Run_History
 

Cause 8: Dashboard shows running on CMDB UI as the pod restarts in between the util run

Solution 8: 

1. From mid-tier open CMDB:Dashboard_Utility_Run_History
2. Check for the entry that shows running
3. Set status Aborted
4. Save the entry

This will set the CMDB util run to Aborted and on CMDB dashboard the previous date's successful run will be shown.

Next run should work fine if no restart of pods during the util run.