Bookshelf Home | Contents | Index | Search | PDF |
Siebel Data Warehouse Installation and Administration Guide > DAC Functional Reference > About the DAC Design View >
About the DAC Execution Plans Tab
The Execution Plans tab displays a list of execution plans in the top pane. This list includes the execution plan name and an Inactive column, which indicates whether the execution plan is active or inactive. Inactive execution plans do not participate in the ETL process.
Table 19 provides a description of the subtabs in the bottom pane.
Actions Available
The following actions are available in the top pane toolbar and in the right-click menu when the Executions Plan tab is active.
Preview Command
This command generates a preview of all tasks and their dependencies by reviewing the subject areas, table groups, tables, and tasks. Information provided includes the approximate order in which tasks are executed, a list of source tables, target tables, and tables for which an image will be built. Only the tasks that source or write to database connections as defined in the execution plan are included. For more information about the Preview functionality, see Using the DAC Preview Functionality to View Tasks and Dependencies.
Copy Record
This command creates a copy of the selected execution plan and also copies the references to subject areas and database connections.
Generate Index Scripts Command
This command generates drop index, create index, and analyze table scripts for all the tables that participate in the ETL process. The results are stored in the log\scripts directory. The index scripts are separated by ETL indices and query indices. The DAC server automatically drops and creates indices and analyzes the tables. This option can be turned off by setting the system preferences. It is recommended that this option be turned off only for DB2-390 environments.
Run Now Command
This command submits a request to the DAC server to execute the execution plan. Inactive execution plans are not included in the process.
When an execution plan is run, the following logic is used to identify the tasks that need to be run and their order of execution.
- Check on the previous run status.
- If the previous run executed a different execution plan from the one currently submitted (either manually or through the scheduler), abort the run.
- If the previous run executed is the same as the current execution plan and did not complete, continue from where it left off.
- If the previous run has completed, create a new run.
- Check resources.
- Select initial tables.
- Recursively select related tables.
- Select initial tasks.
- Recursively select all tasks.
- Select optional tasks.
- Select dependencies.
- Identify the task details.
- Identify the list of source tables for change capture and create tasks for change capture and sync for Siebel sources.
- Execute pre-ETL tasks. If there are errors, stop the run.
- Execute the change capture process. If there are errors, stop the process.
- Execute the dependency graph. If there are errors, stop all the tasks that depend on the failed tasks. Continue to execute all others, until there are no more to run, and then stop.
- Execute the change capture sync process. If there are errors, stop the process.
- Execute the post-ETL process. If there are errors, stop the process.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Data Warehouse Installation and Administration Guide Published: 11 March 2004 |