ODI FAQS and Interview Questions

1. What is a scenario in ODI?

· A scenario is a production-ready version of a component (mapping, package, procedure, or variable)

· It contains generated code (SQL, shell scripts, etc.) based on the component’s current state

· Once generated, the scenario is frozen — further changes to the component do not affect the scenario

2. When should a scenario be generated?

· After a component is finished and tested

· Ensures a stable, reproducible execution of the component in production

3. What types of components can have scenarios?

· Mappings → Single-step execution of the mapping

· Packages → Multi-step ETL process

· Procedures → Executes the procedure as a single step

· Variables → Refreshes or updates the variable

4. What are scenario variables?

· Variables defined in the scenario to parameterize its behavior

· Values can be set at execution time to control logic and flow

5. Where are scenarios stored?

· Stored in the work repository

· Can be exported and imported across repositories

· Can be imported into development or execution repositories

6. How are scenarios displayed in ODI?

· In Designer Navigator → Under the source component in the Projects tree (development only)

· In Operator Navigator → In the Scenarios tree (visible in both development and production)

7. Can scenarios be versioned?

· Yes, scenarios support versioning for change tracking and deployment

· See Chapter 19, Using Version Control for detailed version management

8. How can scenarios be executed?

· Command line execution → For automated scripts or CI/CD

· ODI Studio → Run interactively from the GUI

· Scheduler → Built-in agent scheduler or external scheduler for automation

9. Why use scenarios instead of direct components in production?

· Provides a stable, frozen version of the code

· Prevents unintended changes in production execution

· Supports reproducibility, scheduling, and deployment across environments

1. What are the main tasks when using Load Plans in production?

· Starting, monitoring, stopping, and restarting Load Plans

· Scheduling Load Plans

· Moving Load Plans across environments (Exporting, Importing, Versioning)

2. How can Load Plans be executed interactively in production?

You can:

· Execute a Load Plan → Run it immediately

· Restart a Load Plan Run → Resume failed steps according to Restart Type

· Stop a Load Plan Run → Abort the execution

3. How are Load Plans scheduled?

· Use ODI’s built-in scheduler or an external scheduler

· Schedule can include scenarios or Load Plans

· Allows automated execution at defined times

4. How are Load Plans moved across environments?

· Through Exporting and Importing between repositories

· Load Plans can be exported from development and imported into production

5. How do you export a Load Plan?

· Can export a single Load Plan or multiple Load Plans at once

· Child objects (steps, schedules, variables) can be included

· Scenarios referenced by the Load Plan are NOT exported and must be exported separately

6. How do you import a Load Plan?

· In development repository → Use Designer or Operator Navigator

· In execution repository → Use Operator Navigator only

· Referenced scenarios must be imported separately

7. How is versioning handled for Load Plans?

· Load Plans can be deployed and promoted using versions and solutions

· Supports production promotion and version control

8. Why export/import scenarios separately from Load Plans?

· Load Plans reference scenarios but do not contain them

· Ensures independent management and versioning of scenarios

9. What is the benefit of scheduling Load Plans?

· Enables automated, repeatable execution

· Reduces manual intervention in production runs

· Supports timely execution of ETL processes

10. Why is versioning important for Load Plans?

· Tracks changes and updates

· Facilitates promotion from development to production

· Maintains consistency across environments