Teradata Unity 16.00 was released to support Teradata Database 16.00 compatibility so Unity customers can now move forward with upgrades to their 16.00 Teradata Database release. In addition to Teradata Database compatibility some of the new capabilities provided in this release include:
Unity 16.00 Passive Routing as an independent product offering and support has been extended to Teradata Systems in the Public Cloud. With on premise Unity servers, business users can now be directed to new Teradata Database Cloud instances used for data labs, isolated sandboxes or to manage seasonal workloads. There is also a new Passive-only mode in Unity 16.00 that will avoid all parsing of incoming requests thus alleviating any parsing overhead associate with read-only sessions.
Unity 16.0 includes operational improvements that include:
Unrecoverable table fault isolation – When a write that includes a read – say an insert into a select from b - fails on one system but succeeds on another, then table ‘a’ (the written table) becomes interrupted so that it can be recovered later and now table ‘b’ (the read table) becomes read only on that same system. This isolates the fault so that a later write to table ‘b’ before table ‘a’ is recovered is not allowed. That way table ‘a’ can still be recovered. Without this feature table ‘a’ would be unrecoverable if it is recovered after table ‘b’ had changed.
Recovery from sync-from point enables a system to continue with the recovery operation from the point where the first table was unrecoverable.
With this feature when the following happens:
1 Ins into A;
2 Ins into B sel from A;
3 Ins into C sel from B;
If table A becomes unrecoverable step 1, then table B and C will be interrupted rather than instantly unrecoverable at steps 2 and 3. Then if you manually resync table A and then activate it (- issue an ”Activate synched from <system> command”) unity will be able to recover tables B and C.
New unityadmin command line to use tdwallet secure password storage to avoid plain text passwords.
A new alert - if a user falls through the defined user mapping and uses the default routing rule an alert will help identify these users that have not been properly mapped.
Ability to track overall availability, as seen by client applications, as well as availability of individual Teradata system