Maximo Open Forum

 View Only
Back to discussions
Expand all | Collapse all

Maximo Report error - intermittent scheduled reports - BMXAA5480E - The report com_inventory_balance_tbl.rptdesign of the INVENTOR application failed to run

  • 1.  Maximo Report error - intermittent scheduled reports - BMXAA5480E - The report com_inventory_balance_tbl.rptdesign of the INVENTOR application failed to run

    Posted 03-21-2024 11:55

    Maximo Report error intermittent on scheduled report -

    This issue started after upgrading servers from 2012R2 to 2019 for the Application and Integration servers.

    Reports are set to run on the integration server.

    Reports run fine one day, next day three reports error, or two reports error, is its endless cycle.

    Deleted the reports schedule, rescheduled reports.

    Regenerated all of the reports.

    Servers have been restarted. 

    URLS match reportsched table

    nothing in the reportjob or reportrun queue.

    Suggestions or Ideas, this is happening on all scheduled reports,  you can manually run the report successfully.

    ERROR 

    [INVENTOR] com_inventory_balance_tbl.rptdesign

    psdi.util.MXApplicationException: BMXAA5480E - The report com_inventory_balance_tbl.rptdesign of the INVENTOR application failed to run.
    BMXAA5476E - The report com_inventory_balance_tbl.rptdesign could not be prepared to run.
    BIRT Report Engine not initialized properly for this operation to work.
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.runReport(ReportAdminService.java:3741)
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.runReport(ReportAdminService.java:3659)
    at com.ibm.tivoli.maximo.report.birt.queue.ReportQueueManager.runQueuedReport(ReportQueueManager.java:960)
    at com.ibm.tivoli.maximo.report.birt.queue.ReportQueueManager.runQueuedReport(ReportQueueManager.java:859)
    at com.ibm.tivoli.maximo.report.birt.queue.ReportQueueManager.doWork(ReportQueueManager.java:660)
    at com.ibm.tivoli.maximo.report.birt.queue.ReportQueueManager$ReportRunThread.attemptToRunReport(ReportQueueManager.java:515)
    at com.ibm.tivoli.maximo.report.birt.queue.ReportQueueManager$ReportRunThread.run(ReportQueueManager.java:454)
    Caused by: psdi.util.MXApplicationException: BMXAA5476E - The report com_inventory_balance_tbl.rptdesign could not be prepared to run.
    BIRT Report Engine not initialized properly for this operation to work.
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.prepareReportDesignForRun(ReportAdminService.java:2537)
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.prepareReportDesignForRun(ReportAdminService.java:2461)
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.prepareReportForRun(ReportAdminService.java:2211)
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.runReport(ReportAdminService.java:3701)
    ... 6 more
    Caused by: java.lang.IllegalStateException: BIRT Report Engine not initialized properly for this operation to work.
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.updateRuntimeReportDesign(ReportAdminService.java:5451)
    at com.ibm.tivoli.maximo.report.birt.admin.ReportAdminService.prepareReportDesignForRun(ReportAdminService.java:2514)
    ... 9 more


    #Reporting

    ------------------------------
    Diane Nohner
    City of Minneapolis
    ------------------------------


  • 2.  RE: Maximo Report error - intermittent scheduled reports - BMXAA5480E - The report com_inventory_balance_tbl.rptdesign of the INVENTOR application failed to run

    Posted 03-22-2024 09:03

    Hi Diane,

    you need to look at the earlier log entries to see what was happening with the JVM.

    The fact that it runs fine on the first day suggests that there is a problem caused by the reports that it is running on/after the first day.

    I would look at the log entries for messages about the available memory being very low.

    Are there any heapdumps/coredumps/javacore files being generated on the server in the profile directory?

    Have a look at the logs from the end of the first day and see which reports were being run. I suspect that you will find that one of the reports is using a lot of memory.

    If you are in stuck then reach out to me privately and I can help further



    ------------------------------
    mark robbins
    Cohesive
    IBM Champion 2017-2023 Inclusive
    See my blog on Maximo support related topics here:
    https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
    ------------------------------

    Original Message


Related Content