Initial debugging of TSCO AutoETL functionality available via the Gateway Manager UI

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:

    TrueSight Capacity Optimization


    APPLIES TO:

    BMC TrueSight Capacity Optimization 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0



    PROBLEM:

    In TrueSight Capacity Optimization (TSCO) I have defined my Gateway Servers in the Gateway Manager UI and I've configured AutoETL for the run.  Although data collection, transfer, and processing is working correctly on the Gateway Server side, computers are not being imported into CO by the AutoETL created ETL runs.  What is the process to identify why data isn't being imported into TSCO?


    SOLUTION:

    The basic workflow of the TrueSight Capacity Optimization (TSCO) AutoETL functionality is:

      (1) Each night the Administration -> ETL & System Tasks -> System Tasks -> 'Gateway Server Admin Helper' task runs and queries the Gateway Server for a list of Manager runs.

    TSCO version 10.0 note: In TSCO 10.0, the task is called "BCOE Administration Helper" but it function the same way.

      (2) This list if active Manager runs is then compared against an internal list of known Manager runs.

    If there are additional runs then they will be added to an existing ETL Task that is contained in one of the existing GatewayServer_[console]_#_0 chains (one per ETL Engine where Gateway Server ETLs can be scheduled).  If there aren't an existing ETLs available (because they are already processing the maximum number of Manager runs) then a new ETL task will be created and assigned to the chain.

    If runs have been removed then they will be automatically removed from their existing ETL Manager Runs list.  If that would leave the ETL empty (managing no ETLs) then the list of Manager runs will be changed to "##EMPTY" for that ETL.

    So, the first thing to check under Administration -> Gateway Manager -> List Nodes is whether the Manager run that isn't importing data into CO is listed and what the associated ETL ID is for that run (the last field in the table).  Next, under Administration -> ETL & System Tasks -> ETL Tasks check the log associated with that ETL.  Did that ETL execute properly?  Does it list that it found and imported that Manager run's vis file?

    The most common reasons for AutoETL configured Manager runs are:

       
    • The ETL did not execute.  This could be for many reasons, such as the BCO Scheduler that the AutoETL run is scheduled is failing or the ETL has been manually unscheduled.
    •  
    • The 'Gateway Server Admin Helper' task is failing and thus new Manager runs are not being associated with an ETL
    •  
    • There is not an ETL associated with the Manager run (this may be because the ETL has been manually deleted)
      

    Additional Information

    Some key points about AutoETL:  
       
    •  Once a Manager run has been associated with ETL AutoETL does not validate that the ETL exists for future runs so if an ETL has been deleted the Manager run will no longer be associated with an active ETL.
    •  
    •  If the ETL runs are scheduled to execute before the Manager run has finished the Visualizer file imported into CO will be delayed by one day.
    •  
    •  In TSCO 10.3 and earlier, there is no UI for changing global parameters associated with AutoETL runs.  Any changes to AutoETL runs need to be done via direct SQL run against the TSCO database.
      

    Useful SQL:

       --
    -- SQL to select the list of Manager runs associated with each ETL associated with AutoETL
    --
    SELECT
          t.name
        , tpp.value
    FROM
          task_pset_props tpp
        , task_pset tp
        , task t
    WHERE
            tpp.name = 'extract.bpa.gm.run.list'
        AND tpp.taskpsetid = tp.taskpsetid
        AND t.taskid = tp.taskid
        AND tp.taskid IN (
                SELECT
                    taskid
                FROM
                    task
                WHERE
                      taskid IN (SELECT  bar.taskid FROM  bcoee_autoetl_runs bar)
                  AND t.name LIKE '%GatewayServer%'
            );
            
    --
    -- SQL to select the list of Manager runs associated with ETLs not registered with AutoETL
    --
    SELECT
          t.name
        , tpp.value
    FROM
          task_pset_props tpp
        , task_pset tp
        , task t
    WHERE
            tpp.name = 'extract.bpa.gm.run.list'
        AND tpp.taskpsetid = tp.taskpsetid
        AND t.taskid = tp.taskid
        AND tp.taskid IN (
                SELECT
                    taskid
                FROM
                    task
                WHERE
                      taskid NOT IN (SELECT  bar.taskid FROM bcoee_autoetl_runs bar)
                  AND t.name LIKE '%GatewayServer%'
            );

      

     


    Article Number:

    000310761


    Article Type:

    Solutions to a Product Problem



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