Specifying ETL cut-off dates
When you transfer data to the reports data warehouse, you can control the amount of data that is transferred by specifying a fixed cut-off date in the past. This approach limits the amount of historical data that is loaded into the reports warehouse and potentially reduces the duration of the ETL run. This is particularly useful for a first-time ETL run.
Use the set_etl_cutoff.nsh script, located in the etl/bin directory, to specify the date after which data needs to be transferred during an ETL run. This script runs the SET_ETL_CUTOFF scenario, which sets the specified cut-off date.
Run the set_etl_cutoff.nsh script before running ETL to ensure that data from the specified cut-off date up to the most current data is transferred.
To specify a cut-off date for data transfer
- From a command line, start the .
Enter the following command:
./set_etl_cutoff.nsh -s <siteId> -v <blVersion> -c <cutoffDate>In this command, the variables are as follows:
- <siteId> is the site ID. This should be a valid site ID from the BL_SITE table.
You can determine the site ID using the show site command. For details, see Report-Administration-Utility-commands. - <blVersion> is the version number of from which data needs to be transferred.
Do not include periods in the version number.
For information about the versions that work with , see BMC-Server-Automation-requirements. <cutoffDate> is the date after which data needs to be transferred, using the following format:
YYYYMMDDFor example, to use January 1, 2009 as the cut-off date, specify the following:
20090101You cannot specify a date after the current date or before January 1, 1900.
If you have previously specified a cut-off date, you cannot specify a new cut-off date that is older than the first cut-off date. For example, if you specify January 1, 2009 as the cut-off date, you cannot specify December 30, 1999 or November 1, 1998 as dates. You can specify January 25, 2009.
- <siteId> is the site ID. This should be a valid site ID from the BL_SITE table.