Common to All Components¶

sso.url=https://solution-manager.acme.com:19443
sso.token-enabled=true

Virtual DataPort¶

1. In the databases where you enabled VCS, push the changes to the new repository.

2. Query at least one base view of each data source to validate the connection to the source.

   Execute views that have the cache disabled so the query hits the source and not the cache database.

   If a connection to a source fails, it may be because the connection requires an SSL certificate that needs to be imported to <DENODO_HOME_8_0>/jre/lib/security/cacerts.

   If a connection to a secure LDAP source fails (possibly with a No subject alternative DNS name matching <HOSTNAME> found error), check this article in the Denodo Knowledge Base.

3. If you got a warning indicating that one or more views were using the parameter QUERYPLAN, do this:

   1. Enable the cost-based optimizer.

   2. Gather the statistics of this view and the subviews of this view.

   3. Obtain the query plan of the view to see if it is the same it was indicated by the parameter “QUERYPLAN”.

4. Views with cache mode full: if you configured the cache engine of the version 8.0 to use a different catalog/schema, the cache of the views with mode full or partial - explicit loads is empty. Therefore, the queries to these views will return 0 rows. You either need to run the Scheduler jobs that load the cache of these views (if you have them) or load them manually.

   Execute this to find the views whose cache needs to be loaded:

   SELECT database_name, name
   FROM get_views()
   WHERE view_type IN (0, 1) AND cache_status in (3, 4, 5);
   

   To load the cache of these views from the VQL Shell, follow these steps. Note that doing this may take a long time. During this time, you cannot close the tab VQL Shell of the Administration Tool.

   1. Select the check box Retrieve all rows and set Limit displayed rows to a high number (e.g. 999999)

   2. Execute this query. This returns the statements to load the cache of the views that require it:

      SELECT 'SELECT * FROM "' || database_name || '"."' || name || '"
          CONTEXT (''cache_preload''=''true'', ''cache_invalidate'' = ''all_rows'',
              ''cache_wait_for_load''=''true'', ''cache_return_query_results'' = ''false'');' AS query
      FROM get_views()
      WHERE view_type IN (0, 1) AND cache_status in (3, 4, 5);
      

   3. Copy all the rows (click a row of the result and press Ctrl+A).

   4. Paste the rows on the VQL Shell and click Execute to execute all the queries.

   These queries will load the cache of the views with mode full or partial - explicit loads.

5. Materialized tables: when you import the metadata from version 7.0, the materialized tables are created but they are empty. The VQL file includes the metadata but not the data.

   Execute this query to obtain the list of materialized tables:

   SELECT database_name, name
   FROM get_views()
   WHERE input_view_type = 3;
   

6. If in the version 7.0, you enabled Kerberos authentication in Virtual DataPort, it is now enabled in version 8.0.

   If during the upgrade process, you created a new Kerberos Service Principal Name (SPN) for this installation, open the Kerberos configuration of this Virtual DataPort and change the SPN and upload the new keytab file.

   In the subsection Kerberos of the page Preparing to Upgrade, we discuss when you need to create a new SPN.

7. DenodoConnect components: the VQL file obtained from Virtual DataPort 7.0 includes the DenodoConnect components you had installed. As you have imported this file, their functionality is also available in your Denodo 8.0 server because the DenodoConnect components for Denodo 7.0 are compatible with Denodo 8.0.

   There is a new version of the DenodoConnect components specific for 8.0. You can download them from DenodoConnects - 8.0. To import them, open the wizard of the menu File > Extensions management. In the tab Extensions, click Import. You will have to confirm that you want to replace the existing extensions.

   Although it is not required, we recommend upgrading the DenodoConnect components with the ones specific for the version 8.0 because in the future, there may be enhancements that are added to DenodoConnect components for version 8.0 but not for the previous versions.

8. In the databases where you enabled VCS, push the changes to the new repository.

9. In the client applications that connect to Virtual DataPort 8.0, upgrade the JDBC driver they use to connect to Denodo.

   The driver is not compatible across major versions. I.e. you cannot use the JDBC driver of the 8.0 version to connect to previous major versions of Denodo nor use the JDBC driver of a previous version to connect to Denodo 8.0.

   If in your applications, the connection URL to Denodo has the parameter “reuseRegistrySocket”, remove it. Otherwise, the connection will fail. This parameter has been removed (see more about this in the section JDBC Driver: Property reuseRegistrySockets of this guide).

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

SELECT property_value
FROM GET_PARAMETER()
WHERE input_property_name = 'java.env.DENODO_OPTS_START'
      AND input_is_web_container_property = TRUE;

WEBCONTAINER SET 'java.env.DENODO_OPTS_START' = '-Xmx2g -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -Dorg.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true';

Virtual DataPort Administration Tool¶

Changes to the Virtual DataPort Administration tools:

1. 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.

2. If you enabled Kerberos authentication, you have to enable it in the administration tools as well.

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

Data Catalog¶

Log in to Data Catalog with an administrator account.

Scheduler¶

If in the version 7.0, you installed DenodoConnect plugins for Scheduler, download these plugins from the Denodo Support Site, for the new version 8.0. Then, remove the existing plugins and import the new ones.

If you created a new Kerberos Service Principal Name (SPN) for this installation of Denodo, open the Kerberos configuration of Scheduler and change the SPN and upload the new keytab file.

Scheduler Index¶

Solution Manager¶

External Applications: Upgrade the JDBC and ODBC Drivers¶

In the applications of your organization that connect to Denodo using the JDBC driver, replace the driver with the new driver of Denodo 8.0. The Denodo JDBC driver is not compatible across different major versions. That is, the driver of version 8.0 cannot connect to version 7.0 and the driver of 7.0 cannot connect to 8.0.

The JDBC driver of Denodo 8.0 is available in the Denodo Community (Home / Drivers / JDBC).

Also, upgrade the Denodo ODBC driver on your applications. Even though, the ODBC driver of 7.0 may be able to connect to Denodo 8.0, the compatibility is not guaranteed and it is an unsupported configuration. Note that you cannot install both the ODBC driver of 7.0 and 8.0 on the same computer.