1. 4 Copyright © 2006, Oracle. All rights reserved. Managing OWB Life-Cycle Changes

2. 4-2 Copyright © 2006, Oracle. All rights reserved. Objectives After completing this lesson, you should be able to do the following: Use OWB Change Manager to take “snapshot” versions of metadata, compare them, and restore them if necessary Use Metadata Dependency Manager to perform impact analysis and determine which objects need to be changed Reimport changed sources into the repository and then deploy changes to targets

3. 4-3 Copyright © 2006, Oracle. All rights reserved. Managing OWB Life-Cycle Changes OWB provides tools to resynchronize changes among data sources, the OWB repository, and the target schema Reimport: Update the OWB repository Redeploy: Update the target schema Data source Target warehouse OWB repository Reimport Redeploy

4. 4-4 Copyright © 2006, Oracle. All rights reserved. Manage Life-Cycle Changes in OWB Sources, Metadata Repository, Targets 1. Change Channels. 5. Invoke Impact Analysis Diagram. 2. Take snapshot before change. 7. Take snapshot after change. 4. Reimport Channels metadata. 3. Change source Channels. 6. Synchronize mapping tables. 8. Deploy changes: Replace mapping. 10. Redeploy the original: Replace mapping again. 9. Cancel change!! No problem. Simply restore original snapshot! Sorry…

5. 4-5 Copyright © 2006, Oracle. All rights reserved. 1. Change Channels. 9. Cancel change!! Manage Life-Cycle Changes in OWB Sources, Metadata Repository, Targets 5. Invoke Impact Analysis Diagram. 2. Take snapshot before change. 7. Take snapshot after change. 4. Reimport Channels metadata. 3. Change source Channels. 6. Synchronize mapping tables. 8. Deploy changes: Replace mapping. 10. Redeploy the original: Replace mapping again. No problem. Simply restore original snapshot! Sorry…

6. 4-6 Copyright © 2006, Oracle. All rights reserved. 1. The CHANNELS Table Requires Modification A sales manager wants a Channel_Status column added to the CHANNELS source table. This source table change cascades to: –OWB metadata definitions of the source –OWB ETL mapping definitions using the source –OWB target table definitions based on the source –Already deployed target tables that are populated from the source

7. 4-7 Copyright © 2006, Oracle. All rights reserved. 2. Take Metadata Snapshot Before the Change

8. 4-8 Copyright © 2006, Oracle. All rights reserved. Finish Defining the Snapshot

9. 4-9 Copyright © 2006, Oracle. All rights reserved. Examine the Snapshot

10. 4-10 Copyright © 2006, Oracle. All rights reserved. 3. Add a Column to the Source Table /* Add the Channel_Status column to the CHANNELS table in the source XSALES schema */ ALTER TABLE channels ADD (channel_status varchar2(20)); commit;

11. 4-11 Copyright © 2006, Oracle. All rights reserved. 4. Reimport the Source Table Metadata The same interface is used for importing metadata and reimporting it. Matching of objects is based on the physical name. Reimporting replaces object definitions. Certain object attributes can be protected.

12. 4-12 Copyright © 2006, Oracle. All rights reserved. Reimport Steps A.Within a module, invoke the Import utility. B.Filter objects. C.Select objects. D.Set reconciliation options. E.Run the utility and view the resulting report.

13. 4-13 Copyright © 2006, Oracle. All rights reserved. A. Invoking Import

14. 4-14 Copyright © 2006, Oracle. All rights reserved. B. Filtering Objects

15. 4-15 Copyright © 2006, Oracle. All rights reserved. C. Selecting Objects Previously imported objects are styled in boldface.

16. 4-16 Copyright © 2006, Oracle. All rights reserved. D. Setting Reconciliation Options

17. 4-17 Copyright © 2006, Oracle. All rights reserved. E. Viewing the Import Results Report Revert New column created

18. 4-18 Copyright © 2006, Oracle. All rights reserved. Dangling Reference: Example A foreign key constraint that does not match the referenced primary or unique key constraint. To resolve this problem, do either of the following: –Reimport the table containing invalid keys and the references will be automatically fixed. –Use the editor to manually update the relationships.

19. 4-19 Copyright © 2006, Oracle. All rights reserved. Reimport Limitations There is no provision for deleted objects. However, dependent objects, such as columns or constraints, are processed.

20. 4-20 Copyright © 2006, Oracle. All rights reserved. 5. Run Impact Analysis Diagram Changed source table In XSALES Affected Dimension in SALES_AW Affected mappings XSALES

21. 4-21 Copyright © 2006, Oracle. All rights reserved. 6. Synchronize the Mapping Tables Synchronize into mapping, to add CHANNEL_STATUS to mapping table.

22. 4-22 Copyright © 2006, Oracle. All rights reserved. 7. Take Metadata Snapshot After Change

23. 4-23 Copyright © 2006, Oracle. All rights reserved. Use Change Manager to Compare Snapshots

24. 4-24 Copyright © 2006, Oracle. All rights reserved. Comparison Results = Exists in one snapshot = Exists in both snapshots

25. 4-25 Copyright © 2006, Oracle. All rights reserved. 8. Deploy the Changes REPLACE

26. 4-26 Copyright © 2006, Oracle. All rights reserved. The sales manager informs you that the decision to implement the new Channel_Status column in the CHANNELS source table has been canceled. This is not a problem for OWB. Simply restore the original snapshot and redeploy. 9. Cancel the Change Sorry…

27. 4-27 Copyright © 2006, Oracle. All rights reserved. 10. Redeploy the Original Version

28. 4-28 Copyright © 2006, Oracle. All rights reserved. Cut/Copy/Paste and Recycle Bin Cut/Copy/Paste functionality –Handles all objects in the repository The recycle bin holds all deleted objects (can cross sessions); preference can be set to “empty on exit.” Clipboard holds only the last cut or copied object.

29. 4-29 Copyright © 2006, Oracle. All rights reserved. Summary In this lesson, you should have learned how to: Manage life-cycle changes in Warehouse Builder sources, repository metadata, and target deployments/loads –Use OWB Change Manager to take, compare, and restore “snapshot” versions of metadata –Use Metadata Dependency Manager to perform impact analysis and determine which objects need to be changed –Reimport changed sources into the repository and then deploy changes to targets

30. 4-30 Copyright © 2006, Oracle. All rights reserved. Lab Practice: Applying Metadata Changes This practice covers the following topics: Using reimport to apply source metadata changes to the OWB repository Using the Change Manager to create, compare, and manage snapshots of metadata Using the Control Center Manager to apply OWB repository metadata changes to a target schema