TSSR-SA: TrueSight Smart Reporting for Server Automation 19.2.01 becomes unresponsive after adding the TSA-DW component content

Version 13
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Smart Reporting - Server Automation


    COMPONENT:

    TrueSight Smart Reporting for Server Automation


    APPLIES TO:

    TrueSight Smart Reporting for Server Automation 19.2.01



    PROBLEM:

     

    User is following the Truesight Smart Reporting for Server Automation (TSSR-SA) 19.2.01 post-upgrade tasks.

    Step 3 of the post-upgrade tasks involves upgrading the TrueSight Server Automation - Data Warehouse (TSA-DW) component content:

    3. Update the TrueSight Server Automation - Data Warehouse component content. For more information, see Getting the latest views in TrueSight Smart Reporting - Platform.

      


    After completing this step, some environments may encounter an issue where the CPU usage of the TSSR service rises to 100% and remains at this level. Memory usage of the TSSR service may also rise and remain very high.

    This results in the TSSR login page becoming unresponsive preventing the completion of the following downstream post-upgrade tasks:

    4. Refresh the filter list in TrueSight Smart Reporting - Platform.
    or
    9. Run the extract, transform, and load (ETL) process to transfer data from all sites to the reports data warehouse. For more information, see Run the extract, transform, and load (ETL) process.

     


    CAUSE:

    TSSR-SA Defect DRTRR-50


    SOLUTION:

    This issue may arise under two slightly different scenarios:

    Scenario 1:  In some situations, this issue can occur because step 2 (delete cache filters) of the TSSR-SA 19.2.01 post-upgrade tasks was not completed. This usually occurs either because the post-upgrade documentation page was missed during the upgrade OR there was an issue deleting the cache filters which resulted in them not being removed.

    In this situation, if the TSSR URL is still accessible, in spite of the high CPU and memory usage, complete the following steps:

    a) Delete the cache filters by following step 2 of the TSSR-SA 19.2.01 post-upgrade tasks
    b) Delete the TSA-DW component from the TSSR admin console
    c) Run the clear_component.nsh script located in the $BDS_HOME/shared/ConfigurationManagement/ directory
    d) Restart the TSSR service
    e) Place the attached JobActivity.yfx file in the $BDS_HOME/bsa/bi/model/19201/directory

    f) Add the TSA-DW component content again using these steps from the TSSR post-install tasks.

    g) Complete the remaining steps (from step 4 on) of the TSSR-SA 19.2.01 post upgrade tasks:



    Scenario 2: If this CPU/Memory usage issue is encountered but the user did successfully compete step 2 of the TSSR-SA 19.2.01 post-upgrade tasks follow these steps:

    a) Stop the TSSR Service
    b) Execute the following SQL statement on the TSSR Repository schema/DB: (e.g. Yellowfin by default)

    delete from taskschedule where iporg<>1 and schedulesubjectcode='FILTERREFRESH’;
    commit;

    c) Place the attached JobActivity.yfx file in the $BDS_HOME/bsa/bi/model/19201/directory
    d) Start the TSSR Service

    e) Delete the TSA-DW component from the TSSR admin console
    f) Run the clear_component.nsh script located in the $BDS_HOME/shared/ConfigurationManagement/ directory
    g) Restart the TSSR Service

    h)  Add the TSA-DW component content again using these steps from the TSSR post-install tasks.
    i) Complete the remaining steps (from step 4 on) of the TSSR-SA 19.2.01 post upgrade tasks:


    Article Number:

    000183650


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles