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
No comments:
Post a Comment