Tableau general troubleshooting

The following messages and issues can appear when you run the lineage harvester, view a technical lineage or upload the new relations to Data Catalog via Collibra Data Lineage.

Problem

 Solution

You get connectivity issues with a 401001 error code.

Unfortunately, 401001 is a very general error code, returned by a Tableau API, that can refer to many issues, including but not limited to the following:

  • The lineage harvester configuration file was configured with the wrong password or Tableau site ID.
  • SSO authentication was used, which is not supported.

Ensure that the user/token that you intend to use to ingest Tableau assets can authenticate to your Tableau APIs via the command line, from the server on which you intend to install and run the lineage harvester.

You can test your ability to authenticate by making the signin API call, using a cURL command.

You can also try checking the login request that the lineage harvester is sending to the Tableau server.

For complete information and guidance on how to test your ability to connect to the Tableau server and authenticate, see Test connectivity with the Tableau server.

The lineage harvester does not connect to hosts using a proxy server.

Technical lineage does not support proxy server authentication, but you can connect to a proxy server. For complete details, including the necessary commands, see Connecting to a proxy server.
You get a TCP timeout error.

To avoid TCP timeout errors, try configuring the Linux TCP keepalive setting:

  1. Edit your /etc/sysctl.conf file:
    # vi /etc/sysctl.conf
  2. Add the following settings:
    net.ipv4.tcp_keepalive_time = 60
    net.ipv4.tcp_keepalive_intvl = 10
    net.ipv4.tcp_keepalive_probes = 6
  3. To load the settings, run the following command:
    # sysctl -p
The designation "UNDEFINED" is shown in the technical lineage. If you are using a Tableau <source ID> configuration file, ensure that you have specified a value for the relevant collibraSystemName property.

You get the following error message or a similar certificate error:

Source '<data source name> failed with exception: javax.net.ssl.SSLHandshakeException: General SSLEngine problem

This message appears when the proxy server sends an unexpected certificate to the lineage harvester or when the default Java truststore is empty or outdated.

First update Java and rerun the lineage harvester to see if that resolves the issue. If the same error message is shown, try the following:

Note In the following example commands, we refer to the techlin-gcp-us server. You should refer to the correct CollibraData Lineage server in the geographic location of your Collibra Data Intelligence Cloud environment.

  1. Run the following command to extract the certificate from the Tableau server:
    keytool -printcert -rfc -sslserver techlin-gcp-us.collibra.com:443 > tableau-cert.crt
    Tip Replace the URL techlin-gcp-us.collibra.com with the URL for your Tableau server, which you specify in the lineage harvester configuration file. This will create a file called tableau-cert.crt in the folder where you run this command.
  2. Run the following command to find the location of your JAVA_HOME:
    echo %JAVA_HOME%
    The location path will be something like the following: C:\Program Files\Java\jdk-17.0.2
  3. Use the location path of your JAVA_HOME in the following command, to import the tableau-cert.crt file into the cacerts file found above.
    keytool -importcert -file tableau-cert.crt -alias "TableauProdServerCert" -keystore "C:\Program Files\Java\jdk-17.0.2\cacerts"
    Note You can specify as different alias, if you want.
  4. Run the following command:
    keytool -list -keystore "C:\Program Files\Java\jdk-17.0.2\lib\security\cacerts" | findstr "Tableau"

  5. Enter the keystore password.

    Tip The password is typically changeit.
    A list of all certificates that match the Tableau string in the "C:\Program Files\Java\jdk-17.0.2\cacerts" file is shown.
    Tip In the list of certificates, look for the one that you imported in step 3. If it's listed, it means the "C:\Program Files\Java\jdk-17.0.2\cacerts" file has the certificate needed to validate the Tableau server.

  6. Run the following command to have the lineage harvester use the cacerts file that you just updated.
    set JAVA_OPTS=-Djavax.net.ssl.trustStore="C:\Program Files\Java\jdk-17.0.2\lib\security\cacerts" -Djavax.net.ssl.trustStorePassword="changeit"

  7. Run the following command to test the synchronization:
    ./lineage-harvester.bat full-sync -s tableau

Note 
  • In the following example commands, we refer to the techlin-gcp-us server. You should refer to the correct CollibraData Lineage server in the geographic location of your Collibra Data Intelligence Cloud environment.
  • If you want to add an existing certificate to the Java Truststore, instead of creating a new Keystore, replace "<your keystore name>" in steps 2 and 3, with the path to the cacerts file in your Java installation, for example %JAVA_HOME%\jre\lib\cacerts.
  1. Use the following command to get a certificate from the corresponding techlin-gcp-us.com site, which is part of the CollibraData Lineage infrastructure:

    openssl x509 -in <(openssl s_client -connect techlin-gcp-us.collibra.com:443 -prexit 2>/dev/null) -out techlin-gcp-us.crt

    Tip If you already have a correctly formatted certificate on the server, you can skip this step.

  2. Add the certificate to the Java Truststore:
    keytool -importcert -file techlin-gcp-us.crt -alias techlin-gcp-us -keystore <your keystore name> -storepass changeit
  3. Run the lineage harvester and use the new truststore using the following parameter:
    -Djavax.net.ssl.trustStore=<your keystore name>
    Example To synchronize your data sources again, run the following command:
    ./bin/lineage-harvester full-sync -Djavax.net.ssl.trustStore=mykeystore
You get an external system ID mapping error

The error message looks similar to the following:

PROCESSING ERROR: "syncer.domain.DgcSyncError: java.lang.Exception: Unexpected DGC job status: ERROR
Error message: {
"type" : "MESSAGE",
"message" : "A mapping for the external system id 'd0f3a21a2324fa117112409bdea6ade7' and resource '59cf9293-fca1-4f78-99ab-31c150a23626' already exists."
}
Caused by: java.lang.Exception: Unexpected DGC job status: ERROR
Error message: {
"type" : "MESSAGE",
"message" : "A mapping for the external system id 'd0f3a21a2324fa117112409bdea6ade7' and resource '59cf9293-fca1-4f78-99ab-31c150a23626' already exists."
}"

Please create a support ticket and provide your answers to the following two questions.

Note Refer to the example error message above and replace the IDs of the external system and the mapped resource with those in the error message you received.

  • What is the asset type of the mapped asset? In this example, the asset with ID 59cf9293-fca1-4f78-99ab-31c150a23626?
    Tip To view the asset type, go to the following URL: <your-collibra-platform-url>/asset/59cf9293-fca1-4f78-99ab-31c150a23626
  • What is the mapping definition?
    Tip To view the mapping definition, go to the following URL: <your-collibra-platform-url>/rest/2.0/mappings/externalSystem/d0f3a21a2324fa117112409bdea6ade7/mappedResource/59cf9293-fca1-4f78-99ab-31c150a23626

If you are using Collibra Data Intelligence Cloud 2021.11 or older, you have to add all Tableau attributes in the operating model to a scope and create a scoped assignment before you ingest Tableau via the lineage harvester.

Prerequisites

Steps

  1. In the main menu, click , then Settings.
    The Collibra settings page opens.
  2. In the tab pane, click Scopes.
  3. Above the table, to the right, click Add.
    The Create Scope dialog box appears.
  4. Enter the required information.
    FieldDescription
    NameThe name of the scope.
    DescriptionThe description of the scope, for example to add extra details.
  5. Click Save.

  6. Open a Tableau asset type:

    1. In the main menu, click , then Settings.
      The Collibra settings page opens.
    2. In the tab pane, click Asset Types.
      The asset type table appears.
    3. In the overview of asset types, click an asset type.

    The Asset type editor opens.

    Important You need to do this for each of the following asset types:
    • Tableau Project
    • Tableau Site
    • Tableau Workbook
    • Tableau Data Attribute
    • Tableau Server

    There are other Tableau asset types, but they do not require the scoped assignment.

  7. In the tab pane, click Add assignment.
    The Select scope for this assignment dialog box appears.
  8. Select the custom scope that you have created for Tableau assets.
    Note You can only add one scope at a time.
  9. Click Add assignment.
    The settings of the global assignment are copied into the selected scope.
Warning After you've created the scoped assignment, do not change the assignment itself. The sole purpose of the scoped assignment is to ingest read-only attributes for which you normally need a system user.
Note If you ingest Tableau metadata in a Collibra version 2021.09 or older, you must also manually create two new relation types and add them to the Tableau <source ID> configuration file.

In Collibra, the name of a Tableau Data Attribute name is an asterisk (*).

 If you ingest a Tableau dataset that doesn't have any attributes, an asterisk (*) is shown as the Tableau Data Attribute asset name in Collibra.