Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Performing the initial ETL run

Before using BMC Decision Support for Server Automation, you must start the ETL process to transfer data from the BMC Server Automation database to the reports data warehouse. The initial ETL run can take a long time because it is performing a full data load.

After you install BMC Decision Support for Server Automation at the primary BMC Server Automation site, you can run ETL to transfer data from the primary site to the reports warehouse.

The instructions in this topic describe how to run ETL from the command line. You can also create a BMC Server Automation Network Shell Script Job to run ETL. BMC recommends that you create a job for running ETL on a regular basis. For more information, see Running-ETL-using-BMC-Server-Automation-jobs.

Before running ETL for the first time, ensure that you have assigned appropriate roles to the users (for example, a primary site user must have the GlobalReportAdmins role). For more information, see Managing-access.

To run ETL for the first time

  1. Navigate to the BDS_HOME/shared/odi/bin directory.

  2. On the reports server, from a command line, start the Network Shell and enter the following command:

    ./run_etl.nsh -s 1  

    Alternatively, from a command line, enter the following command:

    nsh ./run_etl.nsh -s 1  

    The s switch represents the site ID.

This command uses standard values for the command arguments. For detailed instructions about running ETL and a description of the command arguments, see Running-ETL-using-an-NSH-script.

To transfer data from other sites, first add those sites if necessary, and then re-run the run_etl command for each site. For more information, see Adding-sites.

Where to go from here

Adding-sites

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*