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.

Scenario execution dependencies

The following diagram depicts the scenario execution sequence and scenario dependencies: 

The 0_BSARA_ETL scenario runs first and executes scenario runs in the order shown in the previous execution diagram. All scenarios are dependent on the first two scenarios: 1_MASTER and 2_FOUNDATION. The 1_MASTER and 2_FOUNDATION data loads contain reference data that is essential to the other scenarios and must be pre-loaded to ensure that the remaining scenarios run properly. When you run a scenario script, it first loads 1_MASTER and then loads 2_FOUNDATION.

The 4_AUDIT and 4_INVENTORY scenarios are dependent on 3_CONFIG_OBJECTS; therefore, 3_CONFIG_OBJECTS is loaded before them. The 4_UPDATE_COGNOS runs last in the scenario execution sequence.

The run_etl.nsh script runs the scenarios in parallel, subject to the dependencies described in this topic. The number of scenarios that run in parallel depends on the level of parallelism specified by you. The default behavior is to run as many scenarios in parallel as possible (subject to the dependencies).

Note

When running scenarios in parallel, the limits of your database server, such as memory, disk space, or processes, can affect parallel scenario execution and result in database-generated runtime errors. You can limit the number of scenarios that are run in parallel by using a command line argument. For more information, see Running ETL using an NSH script.

The following scenarios are not included in the run_etl.nsh script. You must run them separately as needed:

  • 3_AGENT_LOGS
  • 3_JOB_ACTIVITY
  • 3_JOB_RUN_EVENT
  • 3_SMART_GROUP
  • 4_KPI

You run these scenarios with run_etl.nsh by specifying the related property files and using the -f argument. For more information, see Running ETL using an NSH script.

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.

Comments