Dictionary synchronization has the following features:
Dependency Analysis and Auto-Inclusion
Change Manager Synchronize carries out dependency analysis. This is essentially the process of determining whether an object in the synchronization source can be created or modified in the destination. For example, a table must have a schema (and thus, a user) at the destination in which it is created. An index must have a table upon which it is built, and a view must have one or more tables or other views from which it selects. Dependency analysis processing looks for these objects in the destination, and forms relationships between the dependent object and objects upon which it depends to facilitate correct sequencing of script steps.
Synchronize looks in the source for certain objects that are not found in the destination, and brings them into the synchronization automatically. This is called "auto-inclusion". It means that the user need not worry about including all necessary objects in the synchronization scope specification, as long as the objects are available in the source.
Synchronization of Dependency Objects
Change Manager Synchronize also performs limited synchronization of dependency objects (that is, objects upon which others depend) that are present in both source and destination. In particular, user and role objects identified as dependency objects are synchronized with respect to their grants. This is important because it allows users and roles to be synchronized as needed without including them in the scope specification.
Related Topics
About Dictionary Synchronizations
Dictionary Synchronization Best Practices
Enterprise Manager Information Roadmap
Copyright © 1996, 2010, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.