Smart IT tarda en cargar el dashboard y tiene lentitud

Version 1
    Share This:

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


    PRODUCT:

    Remedy with Smart IT


    APPLIES TO:

    Lentitud, GLEWF calls, consola dashboard, SMT:WorklogView Tambien aplica para Remedy with Smart ITT 18.08



    QUESTION:

    Accesando al dashboard de Smart IT este tiene lentitud y tarda en cargar el dashboard


    ANSWER:

     

    Solucion cuando el problema es la forma SMT:Social_WorklogView:

         
    Analizando los API+FILTER+SQL logs se puede determinar que la causa de la lentitud proviene de llamadas API GLEWF en la forma SMT:Social_WorklogView que pueden demorar demasiado.

    En este ejemplo de abajo se puede ver que el query esta corriendo sobre la tabla T2118 que es SMT:Social_WorkLogView (esto pudiera ser diferente en su ambiente) y que tarda aproximadamente 2 minutos. Esta view se refiere a la view de la base de datos U_SmartIT_Social_Worklogs. Este query esta generandose cuando el usuario accesa el dashboard de Smart IT.

    User-added image
    Query:
    ==================================================
    WITH AR_SQL_Alias$1 AS (SELECT T2118.C1, T2118.C1000000182, T2118.C179, T2118.C1000005261, T2118.C2, T2118.C1000000151, T2118.C1000000159, T2118.C1000000761, T2118.C1000000218, T2118.C1000000655, T2118.C1000001563, T2118.C10001959, T2118.C304309590, T2118.C304309600, T2118.C302308591, ROW_NUMBER() OVER (ORDER BY T2118.C1000005261 DESC, T2118.C1 ASC) AS 'AR_RowNumber_Alias$1' FROM T2118 WHERE (((T2118.C1000000182 IN (SELECT FVALUE FROM #AR704NVARCHAR415)) AND (T2118.C1000005261 > ?)) OR ((T2118.C1000001563 = ?) AND (T2118.C1000000182 = ?) AND (T2118.C1000005261 > ?)))) SELECT AR_SQL_Alias$1.C1, AR_SQL_Alias$1.C1000000182, AR_SQL_Alias$1.C179, AR_SQL_Alias$1.C1000005261, AR_SQL_Alias$1.C2, AR_SQL_Alias$1.C1000000151, AR_SQL_Alias$1.C1000000159, AR_SQL_Alias$1.C1000000761, AR_SQL_Alias$1.C1000000218, AR_SQL_Alias$1.C1000000655, AR_SQL_Alias$1.C1000001563, AR_SQL_Alias$1.C10001959, AR_SQL_Alias$1.C304309590, AR_SQL_Alias$1.C304309600, AR_SQL_Alias$1.C302308591 FROM AR_SQL_Alias$1 WHERE (AR_SQL_Alias$1.AR_RowNumber_Alias$1 BETWEEN ? AND ?) 
    ==================================================
      
       
    • Agregue la configuracion de abajo mencionada en el Centralized Configuration Form de en la seccion: AR Server: com.bmc.arsys.server.shared.

      
    Server-Temp-Table-Threshold: 1000 y luego proceda a reiniciar el AR Server
    (Para este parametro por favor tenga en cuanta estas consideraciones) 

                                 
    SW00551614Value of Server-Temp-Table-Threshold  debe ser menor a 2100 para SQL Server y menos que 1000 para ORACLE. Si configura un valor mayor a estos mencionados obtendra el siguiente error: 
    SQL Server: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL ; SQL state S0001; error code 8003; The incoming request has too many parameters. The server supports a maximum of 2100 parameters. 
    ORACLE: com.bmc.arsys.domain.etc.ARException: ERROR (552): The SQL database operation failed.; ORA-01795: maximum number of expressions in a list is 1000
      
    CASO DE USO 2 (El uso de CPU del AR System Server y de la BD es alto)
    Si los cambios antes mencionados ya han sido hechos y aun existen problemas de performance, pudiera revisar nuevamente los logs de SQL y notaria que los SQL queries tienen demasiados operadores 'OR' como se observa abajo:

    SELECT * FROM (SELECT AR_SQL_Alias$1.*, rownum as AR_RowNumber_Alias$1 FROM
                    (SELECT T7801.C1, T7801.C1000000182, T7801.C179, T7801.C1000005261, T7801.C2, T7801.C1000000151, T7801.C1000000159, T7801.C1000000761, T7801.C1000000218, T7801.C1000000655, T7801.C1000001563, T7801.C10001959,
                    T7801.C304309590, T7801.C304309600, T7801.C302308591
                    FROM T7801 WHERE (((T7801.C1000000182 IN (SELECT FVALUE FROM ARFTS707201276_401_0)) OR ((T7801.C1000001563 = :1 ) AND (T7801.C1000000182 = :2 )))
                    AND ((T7801.C2 = :3 ) OR exists ( select /*+ NO_EXPAND */ 1 from dual where ((T7801.C112 LIKE :4 ) OR (T7801.C112 LIKE :5 ) OR (T7801.C112 LIKE :6 ) OR (T7801.C112 LIKE :7 ) OR (T7801.C112 LIKE :8 ) OR
                    (T7801.C112 LIKE :9 ) OR (T7801.C112 LIKE :10 ) OR (T7801.C112 LIKE :11 ) OR (T7801.C112 LIKE :12 ) OR (T7801.C112 LIKE :13 ) OR (T7801.C112 LIKE :14 ) OR (T7801.C112 LIKE :15 ) OR (T7801.C112 LIKE :16 ) OR
                    (T7801.C112 LIKE :17 ) OR (T7801.C112 LIKE :18 ) OR (T7801.C112 LIKE :19 ) OR (T7801.C112 L IKE :20 ) OR (T7801.C112 LIKE :21 ) OR (T7801.C112 LIKE :22 ) OR (T7801.C112 LIKE :23 ) OR (T7801.C112 LIKE :24 ) OR
                    (T7801.C112 LIKE :25 ) OR (T7801.C112 LIKE :26 ) OR (T7801.C112 LIKE :27 ) OR (T7801.C112 LIKE :28 ) OR (T7801.C112 LIKE :29 ) OR (T7801.C112 LIKE :30 ) OR (T7801.C112 LIKE :31 ) OR (T7801.C112 LIKE :32 ) OR
                    (T7801.C112 LIKE :33 ) OR (T7801.C112 LIKE :34 ) OR (T7801.C112 LIKE :35 ) OR (T7801.C112 LIKE :36 ) OR (T7801.C112 LIKE :37 ) OR (T7801.C112 LIKE :38 ) OR (T7801.C112 LIKE :39 ) OR (T7801.C112 LIKE :40 ) OR
                    (T7801.C112 LIKE :41 ) OR (T7801.C112 LIKE :42 ) OR (T7801.C112 LIKE :43 ) OR (T7801.C60900 LIKE :44 ) OR (T7801.C60900 LIKE :45 ) OR (T7801.C60900 LIKE :46 ) OR (T7801.C60900 LIKE :47 ) OR (T7801.C60900 LIKE :48 ) OR
                    (T7801.C60900 LIKE :49 ) OR (T7801.C60900 LIKE :50 ) OR (T7801.C60900 LIKE :51 ) OR (T7801.C60900 LIKE :52 ) OR (T7801.C60900 LIKE :53 ) OR (T7801.C60900 LIKE :54 ) OR (T7801.C60900 LIKE :55 ) OR (T7801.C60900 LIKE :56 ) OR
                    (T7801.C60900 LIKE :57 ) OR (T7801.C60900 LIKE :58 ) OR (T7801.C60900 LIKE :59 ) OR (T7801.C60900 LIKE :60 ) OR (T7801.C60900 LIKE :61 ) OR (T7801.C60900 LIKE :62 ) OR (T7801.C60900 LIKE :63 ) OR (T7801.C60900 LIKE :64 ) OR
                    (T7801.C60900 LIKE :65 ) OR (T7801.C60900 LIKE :66 ) OR (T7801.C60900 LIKE :67 ) OR (T7801.C60900 LIKE :68 ) OR (T7801.C60900 LIKE :69 ) OR (T7801.C60900 LIKE :70 ) OR (T7801.C60900 LIKE :71 ) OR (T7801.C60900 LIKE :72 ) OR......


    Para este caso de uso agregamos Disable-New-RLS-Implementation  F
    (en la documentacion se menciona que el valor de default es T) 

    Esto mejorara el performance dramaticamente y reducira los costos de uso de CPU

    Nota: Disable-New-RLS-Implementation tiene un impacto en el rls query, si el valor es 'T', el query es hecha usando OR y cuando es 'F' el query utiliza regex para groupos de permisos dinamicos.

    **Cuando el causante de la lentitud es la forma  SMT:Social:FollowConfig form, por favor revise este articulo Article Number 000170189

    NOTA: Este artículo también est disponible en Inglés, usar el siguiente enlace o buscar por el Número de Artículo 000163021. / NOTE: This article is also available in English, use the link below or search by Article Number 000163021.
    Smart IT Dashboard slowness causes unresponsive system

      

     


    Article Number:

    000182455


    Article Type:

    FAQ/Procedural



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