TrueSight Capacity Optimization CLM Services ETL and TSCO Workspace are not in sync

Version 6
    Share:|

    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


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TrueSight Capacity Optimization Capacity Optimization



    PROBLEM:

    The TrueSight Capacity Optimization Workspace is not in synch with data in the CLM infrastructure.

    TSCO shows a lot of Service Offering instances without any children VMs, this instances are active and have deployments in CLM but the Workspace doesn't list this. TSCO shows VMs under services offerings which have been decommissioned  some time ago. TSCO workspace shows configuration metrics which are different as in CLM.
     


    CAUSE:

    The ETL was not running well in Assert Mode when it run the first time, after the first run the ETL is only running in Delta mode and only pick up changes.


    SOLUTION:

    1. Verify the TrueSight Capacity Optimization version. A a defect was found in version 10.7.00 ( QM002369553), please confirm that a version is used which included the Defect, this defect is included in 10.7.01.00.C000010 and 11.0.00.00.C00009 , install at least this CHF version or higher..

    2. Unschedule  the ETL and run it manually in Assert Mode, to do this please add the following following custom property to the Cloud Life Management Service Extractor.

    extract.use.assert.mode = true

    Please keep an eye on the log, in a large environment the ETL might run 2 or more hours and the ETL may run out of memory when running it against a large Cloud Life Management environment with a lot of Service Offering Instances deployed, you may need to increase the ETL_HEAP_SIZE in the customprenv.sh until the out of memory does not occur anymore. You may consider to increase it first to 1024m, if this does not help you may need to increase it up to 2046m.

    3. Once the ETL has completed wait until the metrics are processed and check if the SOI children VMs are displayed in the tree.

    If the SOI children are not are not displayed, please run the ETL in LogLevel 10 and set in Advanced Mode under Loader Configuration the Maximum number of rows for CSV output to -1

    4. It some SOI are still missing look for the name in the log with LogLevel 10, for example on the SOI "SRV171 Windows 2012-Srv-1"

    > INFO [SRV171 Windows 2012-Srv-1]: Starting extraction of SOI (guid: fb2ad6e6-e4fe-4387-f1d-8f709958d6ff, recid:OI-39cfcgag28654b2c99a2fa3fg6ad92dd)
    > INFO [SRV171 Windows 2012-Srv-1]: Skipping SOI - No contract line uri associated with SOI


    The  "No contract line uri associated with SOI" is a pointer, because TSCO is using contract lines in CLM to detect the objects. This missing contract line is causing that the SOI is not picked up. If this is not a production system you can offboard and onboard it in CLM. this should create the contraction lines. If this is not possible you can create contract line entries in CLM. How to do this describes the attached PDF document: CLM How to create contractline entry.pdf, it was created for CLM version 4.6, please work with a CLM Administrator for this.
     


    Article Number:

    000145987


    Article Type:

    Solutions to a Product Problem



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