This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Capacity Optimization
TrueSight Capacity Optimization all version.
Why doesn't an ETL import any data into TrueSight Capacity Optimization (TSCO) when it is configured to run in Simulation Mode? The ETL logs don't report any errors and the ETL appears to be completing successfully.
Simulation ModeThis setting in the TrueSight Capacity Optimization (TSCO) ETL configuration allows you to simulate a connection to the datasource and to make sure the ETL is connecting and finding data. However, in order to import data it is necessary to ensure that the Simulation Mode option is set to false in order to have the ETL execute the LOAD stage of the execution and import data into the database. If that value is not set, the ETL will run through the Extraction and Transformation phases of data collection, but not complete the Load phase which loads data into the TSCO database..
The setting "Execute in simulation mode" must be set to "NO" to be able to extract data from the datasource.
ETL execution data flowWhen an ETL runs the data is Extracted from the 3rd party database and is then any ETL specific data Transformation is performed locally (possibly in memory or using a local flat file database on the ETL Engine side, finally data is Loaded into the staging tables within the TSCO database (SYS_DATA_STAGE for performance data or WKLD_DATA_STAGE for Business Drvier data). That data loaded by the ETL into the staging tables is then read by the Near-real-time Warehouse (NRTWH) component of the Datahub and moved into the DETAIL level tables (at this point it becomes visible in TSCO). Separate threads within the NRTWH then summarize the data from the DETAIL level to the HOUR level and then to the DAY and MONTH level (as well as any necessary statistics calculations being done on the data).
When a ETL is run in Simulation Mode the ETL runs through the normal data Extraction phase and any ETL side data transformation steps are also completed. The ETL completes execution before it runs the loader phase which would actually import the data into the staging tables within the TSCO database.