Skip to main content

Validata release notes

The following are the release notes for Validata 1.1.0.

Known issues

  • The Documentation link on the Alerts page does not go to the correct Configuring alerts page.

  • DVN-1485: can't enter required three-part object names (<database>.<schema>.<table>) required for for Snowflake and SQL Server in UI

    Workaround: Use a connection URL that includes the database name.

  • DVN-1486: dropped tables removed from validation pairs still appear in reports

    Workaround: Create a new validation with the changed table definition.

  • DVN-1561: SQL Server > BigQuery - dropping a column from a table does not reset the validation pipeline to an Error State

    Workaround: Create a new validation with the changed table definition.

  • DVN-1574: Oracle > PostgreSQL Fast Validation - OOS for string and float datatype which is in-sync in other validation

    Workaround: Use Full Record Validation.

  • DVN-1640: Vault not working for TrustStore or KeyStore password

    Workaround: Store the entire connection URL in Vault.

  • DVN-1796: Oracle > Databricks - revalidation fails when composite primary key chosen includes different data types

  • DVN-1808: After dropping a user you cannot create a new user with the same name.

  • When the number of duplicate keys stored in the Validata Historian is very high, the system can become unresponsive. If this happens, Contact Striim support.