Module Owb Lifecycle
Download as PPT, PDF0 likes502 views
The document discusses best practices for managing the lifecycle of OWB (Oracle Warehouse Builder) projects including export, import, deployment to various environments, source control, data migration, and upgrading. It provides examples of development, QA, and production environments and discusses strategies for coordinated releases across systems.
Module Owb Lifecycle
- 1. OWB Lifecycle Export, Import, MDL
- 2. OWB Lifecycle New Feature or Functionality Planned Built in Development Area Tested in QA And/or staging environment Deployed To production
- 3. Change Management Our definition The methods, procedures, and technology used to incrementally introduce changes into our Data Warehouse that lowers risk and increases system stability Know changes introduced!
- 4. Topics Deployment Scenarios Scripts Deployment Manager Multiple “environments” Development/QA/Production MDL / Snapshot One of “many” Source Control Coordinated Release Data Migration Impact Analysis
- 5. Deployment Scenarios Generated Code Create/Drop/Replace/Upgrade “ Deploy to File” Deployment Manager
- 6. Development/QA/Product Development Multiple “dev” instances Zero impact to production users Small Volumes QA One or two instances Used by QA team to test changes (users allowed to “acceptance” test) Medium or Full Volumes Production One or two instances (not RAC term, our term) Used by users to access data, changes impact users and systems Full data volume with significant “window”
- 7. Option 1: Separate Design Reps
- 9. Option 2 : One Design Rep
- 10. Option 2 : One Design Rep Advantages OWB provided comparisons Saves space OWB preferred Disadvantages Not truly “separated” Design Browser for versions Source Control integration
- 11. Impact Analysis VERY USEFUL Establish “depth” of impact
- 12. Source Code Control OWB is not the only part of the “stack” Are there BO or MS reporting configs? shell/ftp scripts for remote retrieval Solution Export objects INDIVIDUALLY and use CVS Separate Design Reps TAG/BRANCH as part of “whole release” Use OMB, etc for build
- 13. Coordinated Release Source systems change GASP! Source X changes Table Y in dev OWB changes Table Y in Source X in dev Source X changes Table Y in QA OWB changes Table Y in Source X in QA Source X changes Table Y in prod OWB changes Table Y in Source X in prod
- 14. Data Migration Situation 3 measures and a new Dimension added to Data Mart Processing 1 day = 1 hour, horizon = 2 years Migration Mappings Consider a custom “upgrade process” update cube set profit = revenue/cost Only used for “releasing”
- 15. Upgrading OWB/Oracle versions Depends on OWB/Oracle prescribed upgrade procedures Consider fresh installations Install new Oracle/OWB Upgrade MDL using utility Import MDL Deploy fresh “warehouse” Process/Copy historical data
- 16. Questions QA hardware purchasing: If one day = 30 minutes to process. T/F : Single Rep can be used with CVS Manually exporting seems tough; how does one automate the build process?
- 17. STUDENT lifecycle select change_info, env_info, good_info from student where present = true and awake = true;