Teradata Unity 16.10 is released and supports Teradata Database and TTU 16.10 and provides several key enhancements that lift several product restrictions, extends passive routing capabilities and delivers key operational improvements.
Change Data Multicast
Unity 16.10 begins the first in a series of Agile product releases intended to deliver a key new architectural enhancement called Change Data Multicast (CDM) to lift Unity feature and functional restrictions. Today there are several limitations related to a Unity implementation. Before Unity is sold to any customer a full Unity assessment is conducted against their current environment to identify if the customer use of Teradata can be leverage in a Unity Environment.
Change Data Multicast provides a new query execution flow within Unity. When the Parser encounters a query from a session it can’t handle through SQL Multicast, Non-deterministic SQL, Unity will leverage Change Data Multicast. The request will be dispatched to a Teradata system that can manage the request. The request will be processed on that Teradata system and the change data captured from that request will be delivered to Unity. Unity will then multicast that change data to all participating systems where those changes should apply. CDM will be delivered in phases with phase one, 16.10, focused on addressing Unity limitations associated with non-determinism.
While there is no definitive number limit built into code for the count of objects that Unity can support, there are theoretical limits based on specific performance bottlenecks related to specific object types. The following improvements were made to the data dictionary so Unity can now handle a larger number of Objects depending on object type.
New routing features
Unity passive routing was enhanced to provide the following options:
Unity Operational Improvements
09/10, Recovery log Usage: 5 GB, Data load Usage: 365 GB
09/11, Recovery log Usage: 72 GB, Data load Usage: 4320 GB
09/12, Recovery log Usage: 12 GB, Data load Usage: 3420 GB
Total time since 'In Service' : 6 days, 15 hours, 7 minutes
Unity Availability : 6 days, 15 hours, 7 mintues (100.000%)
Manage system 'db1' availability : 6 days, 5 hours, 7 minutes (93.715%)
Manage system 'db2' availability : 6 days, 5 hours, 16 minutes (93.810%)
System ID : 2 …
Recovery Type : Object Recovery
Current Step : 3
Recovering Sessions : 1 …