For all Managed Routing sessions, Unity uses a data dictionary to determine the systems an object is available on, and to apply locks to SQL statements.
Objects are added to the dictionary dynamically through DDL statements or with the Unity Dictionary Scanner. The Dictionary Scanner scans dictionaries of 100,000 objects per Teradata Database system. A dictionary of tables and views only can support a large number of objects depending on the table size. Triggers on tables also affect size. Procedural objects, Stored procedures and macros are parsed and may take longer during a scan, but take less time to deploy.
The scanner 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.