For all managed routing sessions, Unity uses a data dictionary to determine the systems on which an object is available, and to apply locks to SQL statements.
Any system-specific DDL are executed using a system-specific passive routing rule.
Macros are also unique in that source code must be included in dictionary deploy and this can cause slower deploys.
The scan time varies from several minutes to a few hours for a large system.
During the dictionary deploy, dynamic DDL updates to the dictionary are on hold. Live transactions that perform DDL are blocked until the deploy and dictionary load is complete. Dictionary deploy times vary from several minutes to a few hours.
To assist in object management, create a separate dictionary for each application you deploy. All dictionaries must be deployed at the same time. You cannot undeploy a dictionary once deployed.
Only one user may edit a dictionary at a time. When you edit a dictionary, a lock prevents other users from editing at the same time. The lock is released when you complete editing or if the user session remains idle for longer than the edit lock timeout. To change the duration of data dictionary editing locks, see Global Settings Tab.