After Importing the Metadata Into the New Installation

After installing the new version of the Denodo Platform and migrating the metadata, perform these steps:

  1. If the cache engine on the previous installation uses the “Generic” cache adapter, copy the files cacheConfig-generic.xml and cacheConfig-generic-unicode.xml of the directory <OLD_DENODO_HOME>/conf/vdp, to <DENODO_HOME_6_0>/conf/vdp.

  2. Compare the log4j.xml files in the subdirectories of <DENODO_HOME_6_0>/conf/ to check if you added more loggers.

    • We do not recommend copy the <logger> elements whose attribute level is set to DEBUG or TRACE. The reason is they were probably inserted during the resolution of a support case.

  3. If SSL is enabled on the previous version, enable it in the new one as well, following the instructions of the section Enable SSL Connections in the Denodo Platform Servers of the Installation Guide. Consider the following:

    • You have to do this for all the servers and their administration tools.

    • The process to enable SSL has changed in Denodo 6.0. It is explained.

    • Copy the KeyStore file (the file of the property to the new installation to continue using the same private key to secure communications.

    • Import the public key of this certificate into the TrustStore of the new installation. Usually it is <DENODO_HOME_6_0>/jre/lib/security/cacerts.

  4. If the connection to any data source or to the cache database is performed using SSL and the certificate used by the source is not signed by a known certification authority, import into the Denodo’s TrustStore (usually, <DENODO_HOME_6_0>/jre/lib/security/cacerts) the public key of the certificate used by that source.

  5. In the clients that will connect to Denodo 6.0, upgrade the JDBC driver they use to connect to Denodo. Consider the following:

    • In Denodo 6.0, the JDBC driver is located at the directory <DENODO_HOME>/tools/client-drivers/jdbc.

    • The driver is not compatible between versions. I.e. you cannot use the JDBC driver of the 6.0 version to connect to previous versions of Denodo nor use the JDBC driver of a previous version to connect to Denodo 6.0.

  6. Whenever is possible, configure the ODBC clients to use the new Denodo ODBC driver instead of the PostgreSQL driver. The performance of the new driver is better.

  7. If in the previous installations, the administration tools of Virtual DataPort have Kerberos enabled, you have to do the same on the administration tools of the new version.

    After importing the metadata to the new installation, if the previous installation is configured to use Kerberos to authenticate users, the new installation will be configured to do that as well.

  8. If you have JDBC data sources that connect to a Teradata database, make sure that the default collation of that Teradata database is binary. The section Access to Teradata explains why this is necessary.

  9. If you are using the support to store the metadata in a Version Control System (VCS), create a different repository to store the metadata of Denodo 6.0. Then change the global VCS settings and the ones for each database so they point to the new repository.

    This is necessary because some VQL statements of Denodo 6.0 are incompatible with earlier versions. Therefore, if you check in elements from Denodo 6.0 and try to check them out from Denodo 5.5, there might be errors.

  10. If in the administration tools of the previous version you increased the query timeout, do the same in the administration tools of the new version.

  11. Do a source refresh of all the JDBC base views that have fields of type “date” and the fields do not have their source type property set. This is necessary to take advantage of the new support for fields that represent date values without time.

    A field of a base view has its source type set when in the CREATE TABLE statement, you see something like sourcetypeid = '-5', next to the type of the field.

  12. Carefully read the section Backward Compatibility, which lists the changes introduced in the versions 6.0, 5.5 and 5.0 that may affect the applications that interact with Denodo.

When upgrading from the Denodo Platform version 4.7, do the following:

  1. Update the “driver class path” of each JDBC data source that points to an Oracle database. If you do not do this, the data source will not use the latest version of the Oracle JDBC driver included with the Denodo Platform. To change this, follow these steps:

    • Edit the data source.

    • Select the value of the field Database URI and press Ctrl+C to copy the value to the clipboard.

    • Select a different adapter and select again the adapter of the appropriate Oracle version.

    • Paste back (Ctrl+V) the URI you copied.

    • Save the changes.

Add feedback