Reviewing BMC ProactiveNet Reporting log files

Report engine logs are located at the following folder:
reportEngineInstallationDirectory/ReportEngine/tools/jboss/server/all/log/reportengine.log

The reportengine.log file is the main log file of the report engine server. This file logs all the information related to event,impact and performance reporting. Review this file for issues related to data collection.

Note

If data gaps are observed in the reports, monitor the following directories to check if the CSV files are generated due to data gaps:

  • reportEngineInstallationDirectory\ReportEngine\tools\jboss\server\all
    \transformations\datagapjob\csvfilesstats
  • reportEngineInstallationDirectory\ReportEngine\tools\jboss\server\all
    \transformations\datagapjob\csvfilesrate

Exceptions/errors in the reportengine.log file

  • ORA-00904: "LASTMODIFIEDTIMESTAMP": invalid identifier

    Verify the database configuration of BMC ProactiveNet Performance Management server registered with the reporting engine using the command:

    bppmr_config.bat register -list from %BMC_PROACTIVENET_REPORTENGINE_HOME%/ReportEngine/bin/reportsCLI/ directory
  • java.lang.OutOfMemoryError: Java heap space
    • Make sure that the Pentaho logging is set to Minimal in the following property:
      reportengine.pentaho.logging.level=MINIMAL

      Do not set the logging level to either Detailed, Debug, or RowLevel logging because it can have implication on memory consumption of the reporting engine. Perform changes with caution for specified time or scenario while simulating a support issue.
      • Error: Only show errors
      • Nothing: Does not show any output
      • Minimal: Uses minimal logging
      • Basic: This is the default basic logging level
      • Detailed: Provides detailed logging output
      • Debug: For debugging purposes, very detailed output.
      • Rowlevel: Logging at the row level, this can generate a lot of data.
    • Tune Heap memory parameters for the report engine as per BMC recommendations.
  • Unable to fill pool org.jboss.resource.JBossResourceException

    Can be caused due to process crunch allocated for database. Check that enough processes are allocated to the database (default is 150). If the database reaches this count, increase the value.
  • ORA-01683: unable to extend index REUPGRADE.PK_STATS_DATA partition PARTITION_20140426 by 8192 in tablespace BPPMR_STATS

    Add a new datafile to the tablespace mentioned in this error.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*