USER MANUALS

Modify the Virtual DataPort Metadata

Before continuing with the migration process, you may need to modify the export.vql file, which contains the metadata of Virtual DataPort.

If you are using the cache engine, do the following:

  1. Open the VQL file.

  2. Search DATASOURCE JDBC vdpcachedatasource and modify the value of the parameter DATABASEURI to point to the new schema of the cache database you created in the section Before Installing a New Version of the Denodo Platform.

  3. Search DATASOURCE JDBC customvdpcachedatasource. There may be several occuren and modify the value of its parameter DATABASEURI to point to the new schema of the cache database you created in the section Before Installing a New Version of the Denodo Platform.

Note:

  • There may be more than one CREATE DATASOURCE JDBC customvdpcachedatasource statement and you have to modify the DATABASEURI in all of them.

  • If you do not find this statement, it means that all the databases use the global configuration of the cache.

  • You may find this statement, but without the parameter DATABASEURI. In this case, ignore this statement and continue searching.

If upgrading from Denodo 5.5 or 5.0:

  • Open the export.vql file generated in the previous section and search 'formatted' = 'yes'.

    For each occurrence of this parameter inside the CONTEXT clause of a CREATE VIEW statement, check that the syntax of the statement is valid in Denodo 6.0. The reason is that in Denodo 6.0 the syntax of a few operators has slightly changed. The section Changes in VQL Syntax lists the changes in the VQL syntax.

If upgrading from Denodo 4.7 or earlier:

  • Modify all the CREATE USER statements that do not have the clause SHA512.

    For example: CREATE USER denodo 'JRSsktQUB1I' ENCRYPTED;

    In these statements, do the following:

    • Remove the ENCRYPTED clause.

    • Enter the password of that user in clear. If you do not know it, set a default one and after the installation, that user will have to change it.

The reason for this change is that Denodo 4.7, before installing the update 20120213, calculated the hash of the user’s password with an algorithm that is no longer supported.

Add feedback