Skip to main content Skip to complementary content

After upgrading Talend Data Catalog

This section describes the actions to do after upgrading Talend Data Catalog.

Reviewing the logs for any automatic upgrade or migration errors

  1. Review the system logs in Manage > System Log.

    It should look as follows in a typical successful upgrade migration:

    MIRWEB_I0044 Starting database upgrade. Product version is 31.31.2 whereas database version is 30.22.2.
       DBUTL_I0031 Updating database from version 30.22.2
       ...
       MIRWEB_S0005 Running operation: Upgrade data mappings to create classifier links
       MIRWEB_S0005 Running operation: Migrate Custom Attributes to Metamodel
       MIRWEB_S0005 Running operation: Migrate Business Glossaries to Metamodel
       MIRWEB_S0005 Running operation: Migrate Term Classification links to Metamodel
       MIRWEB_S0005 Running operation: Migrate Hide Data property to Sensitivity Label
       MIRWEB_S0005 Running operation: Migrate steward of content with the 'Send email notification when an import' option to watcher
       ...
       SEARCH_I0005 Indexing model [463,1].
       ...
       MIRWEB_S0101 Server is initialized.
  2. For automated test purpose, you can search for the following messages in the log:
    • On a successful start/upgrade of the server:
      MIRWEB_S0101 Server is initialized.
    • On a failure to upgrade the server:
      MIRWEB_F0003 Service initialization error:
    • On a failure to start the server:
      MIRWEB_F0004 General error during service initialization:
  3. Review the automated migration operations in Manage > Operations.
    You can find the details for each migration operation and in case of errors on the system log:
    • Upgrade data mappings to create classifier links
    • Migrate Custom Attributes to Metamodel
    • Migrate Glossaries to Metamodel
    • Migrate Term Classification links to Metamodel
    • Migrate Hide Data property to Sensitivity Label
    • Migrate steward of content with the 'Send email notification when an import' option to watcher

Reviewing and testing the changes for basic features previously released

Review the release notes on the new worksheet attributes for object search, explore and edit capabilities or data lineage.

For more information, see Talend Data Catalog Release Notes.

Reviewing and testing the changes for customization features previously released

Review the release notes on the new worksheet attributes for MQL, worksheets, dashboards, presentations or REST API and on the improved metadata query language (MQL) and REST API.

For more information, see Talend Data Catalog Release Notes.

Testing metadata harvesting

As each new version contains new and improved bridges, you should update models only if they have been imported with a connector improved with the new version or only if a new bridge specific to the data source technology is now available. It is recommended to perform the following steps:
  1. Disable the incremental harvesting option for this time.
  2. Re-import the models manually.
  3. Re-build the configurations manually.
  4. If you used remote harvesting servers, you must reinstall new ones based on the new version in a new directory.

    You can copy the data directory from the old installation to reuse the metadata cache for incremental harvesting.

    If you need to have both the previous and current versions of the software to temporarily coexist on the same machine for testing, you must configure the new servers to run on separate ports.

  5. Update the remote harvesting servers in Manage > Servers.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!