Clarity

  • 1.  Jaspersoft Report Blank after Patch

    Posted Dec 12, 2017 10:42 AM

    A couple weeks ago we patched our Jaspersoft Report server to the latest patch (6.2.1_5.2.1.54).

    Of course we got bit by the Scheduled Reports are Blank bug (CA: DE32148, Tibco: 01467237).

    No worries, I went into every scheduled report and clicked save - all those are back and running properly.

     

    I have one outlier: a custom Jaspersoft Studio report that no longer returns data. I believe the patch was the last event before this stopped working. The Jaspersoft Log is not showing any trouble.

     

     

    It feels like one of those 'remap a GUID or Bean' thing. I believe I've executed all the necessary post patch commands properly. I can open a ticket but if this is an easy fix it would be great to capture it here for the next forum traveler.

    Nika_Hadzhikidi & SumanPramanik - any ideas?



  • 2.  Re: Jaspersoft Report Blank after Patch

    Broadcom Employee
    Posted Dec 12, 2017 11:31 AM

    Hi Rob,

     

    I guess your datasource is working and specifc report then we need to see the query and see if the tables/views used in report have data.

     

    Regards

    Suman Pramanik 



  • 3.  Re: Jaspersoft Report Blank after Patch

    Posted Dec 12, 2017 03:48 PM

    I removed the Security join from the report and it works again.

    AND    ((EXISTS (SELECT user_key
                     FROM   dwh_inv_security
                     WHERE  global_view_right = 1
                     AND    user_uid = $P{ppmUser}
                     AND    permission_key = 'ProjectViewManagement'))
            OR
            (EXISTS (SELECT investment_key
                     FROM   dwh_inv_security
                     WHERE  investment_key = I.INVESTMENT_KEY
                     AND    user_uid = $P{ppmUser})))

    Did I miss one of the post patch commands?



  • 4.  Re: Jaspersoft Report Blank after Patch

    Posted Dec 12, 2017 04:14 PM

    DWH_INV_SECURITY has no data.

    All Load Datawarehouse jobs are running & completing successfully.

    Off to open a case.



  • 5.  Re: Jaspersoft Report Blank after Patch

    Posted Dec 12, 2017 05:10 PM

    It's possible the Security Model changes introduced in 15.1 have been back ported to a 14.3 fixpack. I can find this in the 14.3 fixpack 9 readme:

    CLRT-80253: New Security Model for the Data Warehouse.

    Expected Result: Load Data Warehouse Access Rights job runs in a few minutes
    Actual Result:  Load Data Warehouse Access Rights job was taking hours for large customers

     

    If this is it - what is isn't saying is all reports developed against DWH_INV_SECURITY need migrated to DWH_INV_SECURITY_V.

     

    Updating the security joins on our report appears to have fixed this issue. I'll test more tomorrow.



  • 6.  Re: Jaspersoft Report Blank after Patch

    Posted Dec 12, 2017 11:28 PM

    Not sure, but we can check if Load Dataware house access job is running fine and any log messages around this job.



  • 7.  Re: Jaspersoft Report Blank after Patch

    Broadcom Employee
    Posted Dec 13, 2017 12:58 AM

    DWH_INV_SECURITY is no longer used its modified to view 

     

    Release 15.1 Updates (SaaS) - CA PPM SaaS - 15.2 - CA Technologies Documentation 

     

     

    Do you have the user in the view or run the DWH rights job as well as Create Jaspersoft user job. Let me know how it goes.

     

    Regards

    Suman Pramanik 



  • 8.  Re: Jaspersoft Report Blank after Patch

    Posted Dec 13, 2017 05:10 AM

    Suman Pramanik wrote:

     

    DWH_INV_SECURITY is no longer used its modified to view 

    Hi Suman. We are on 14.3 Fixpack 10. I believe we may have jumped from Fixpack 8 to 10 with our last patch. Did the 15.1 Security Schema change get back ported to 14.3 in fixpack 9 or 10? We are on MSSQL.



  • 9.  Re: Jaspersoft Report Blank after Patch

    Broadcom Employee
    Posted Dec 13, 2017 05:17 AM

    This was ported back on 14.3 patch 9

     

    CLRT-80253: New Security Model for the Data Warehouse.

    Expected Result: Load Data Warehouse Access Rights job runs in a few minutes
    Actual Result: Load Data Warehouse Access Rights job was taking hours for large customers

     

    Regards

    Suman Pramanik