Siebel Data Warehouse Installation and Administration Guide > DAC Functional Reference > About the DAC Execute View >

About the DAC Validation Tab

The Validation tab allows you to view the results of a validation. The following kinds of validation are available:

• Resource Validation: Checks to see if the database connections are validated. This will be checked as a first step of the ETL process. If the database connections are not valid, the ETL will abort. This validation is also available on the DAC client through Setup > Database Connections > Test Connection functionality.
• Table Validation: Checks to see if the tables do exist in the database. If the tables do not exist, the ETL will fail. This is not checked during the ETL run. The check also includes verifying the existence of image tables where applicable.
• Index Validation checks the following:
  1. If all the columns in the index definition exist on the table in the database.
  2. If the index does exist in the database, the validation compares the index definition and points out the differences.
  3. If there are multiple indices with the same definitions (columns in the same order) for a table.
  4. If there are indices with the number of columns greater than 255.
  5. If '# Include columns' is greater than the number of columns provided in the index column list.
  6. Checks to see if the index column has no columns.
  7. If the number of columns is more than 16. Some databases allow for more than 16 columns. However, the user should inspect the warning and verify its validity.
  8. If an index on a table was created on the database but not defined in the repository. This may cause the ETL process to fail, because all the indices need to be dropped prior to the load, otherwise the bulk loaders may fail.
• Informatica Workflow Validation: Verify for the task definitions of type Informatica to match the 'Command for Full Load' and 'Command for Incremental Load' do exist in the Informatica repository. For this validation to work, configure the system preferences 'Main Informatica Repository' to point to the database where the Informatica repository resides with the logical name given to the database under Setup-> Database Connections.
• Check for circular dependencies: While defining task dependencies, care should be taken to not to define circular dependencies. For example task A depends on task B, and task B depends on task C, and task C depends on task A. Such occurrences will be identified. If these errors do exist, the ETL will fail.