Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference
  17. Appendix B: PowerCenter Reports Reference

Repository Guide

Repository Guide

Locking Within Objects

Locking Within Objects

Some repository objects contain other repository objects. For example, workflows contain sessions and tasks, sessions contain mappings, and mappings contain at least one source and target definition.
You obtain an in-use lock on an object when you view it. You can view an object used by another object without affecting the other object. However, if you save changes to an object used by other objects, the repository might mark the other objects invalid. Before using invalidated objects, you must validate them.
For example, you open a mapping used by a session, delete a transformation, and save the changes. When you save the mapping, the repository notes the mapping has been changed, and marks the session and every other session using the mapping invalid. The change might invalidate any workflow containing the session.

0 COMMENTS

We’d like to hear from you!