Page tree

Skip to end of metadata
Go to start of metadata

The steps required to import data into the Solaris view are:

Installing the AIX or Solaris view

To install the AIX or Solaris view, refer to Performing system maintenance tasks.

Configuring and running the ETL connector to import data

Note

Repeat these steps for every new integration of data.

To import data into the AIX (or Solaris) dashboard, configure and run the ETL connector for Gateway Server. To determine the most suitable version of the ETL connector, and find information on how to configure see Gateway Server.

For more information, refer to Maintaining ETL tasks.

Artificially modified clocks on managed systems

For some kinds of applications, customers might maintain systems with artificially modified system clocks showing data far into the future. For example, this may be an easy way to test application behavior two years from now. There is no way to get BMC TrueSight Capacity Optimization to import data from such modified systems, nor to analyze such data within BMC TrueSight Capacity Optimization. Following are some details about why.

Assumptions regarding the time period of time series:

There are certain assumptions BMC TrueSight Capacity Optimization makes about the effective time periods of imported time series.

Manipulating future timestamps

BMC TrueSight Capacity Optimization depends on the time stamps in the data source to understand which time period the data is for, to be able to compare the time series to other time series. BMC TrueSight Capacity Optimization makes some assumptions when creating historical summaries of various kinds. For example, the roll statistics tables will not consider future timestamps, and there is no way to create rolling time filters for future time periods like “next month”.

Importing data with future timestamps

The BMC TrueSight Capacity Optimization DWH also has built-in checks to avoid importing data outside the latency period, or future data, so as to maintain the integrity of the DWH.

For example, when loading data, only five days’ worth of future time partitions are already created. Trying to load data with timestamps after this period will generate an “ORA-14400: inserted partition key does not map to any partition” error from the store thread during NRTWH processing. Another example: the “lastcounter” processing when importing data makes assumptions about the time stamps from the data sources.

The BPA agents and application servers use the system clocks of the managed systems to create time stamps in the data. They also make assumptions about the timestamps prior to loading the data into BMC TrueSight Capacity Optimization.

Materializing AIX and Solaris views

AIX and Solaris views will be automatically materialized every day by the AIX ER Materializer and Solaris ER Materializer tasks, respectively; check with your BMC TrueSight Capacity Optimization administrator for more details on the task execution time.

If you want to use the AIX (or Solaris) dashboard immediately after importing data, you need to manually run the AIX ER Materializer (or Solaris ER Materializer) task, as described in Configuring the ER View Materializer task.