IBM Support

IBM Db2 Warehouse known issues and workarounds

Product Documentation


Abstract

This document describes known issues and their workarounds for IBM® Db2® Warehouse. The first table lists open (that is, not yet resolved) issues; the second table lists resolved issues.

Content

Open Issues
RTC/GitHub number Open Issue Affected versions Workaround
GitHub 1061 Some non-letter characters cannot be used in passwords. Otherwise, an "invalid parameter or character" error message is issued. All Versions
When creating a password, do not use any of the following characters:
 ; (semicolon)
 % (percent symbol)
 ' (single quotation mark)
 $ (dollar symbol)
   (space)
RTC 108996 Db2 Warehouse sometimes issues error message SQL6048N, indicating that a communication error occurred during START DATABASE MANAGER processing. All Versions To resolve this:
1. On the head node, log in as a root user and issue the following command:
    docker exec -it Db2wh stop
2. On each node, including the head node, log in as a root user and issue the following commands:
    docker stop Db2wh
    service docker stop
3. Restart the MPP system as described in Starting IBM Db2 Warehouse.
(none) After a schema-level restore operation, ownership of the objects is changed to db2inst1, and metadata regarding authorities and privileges for the objects is lost. 3.2.0 and later Before restoring a schema-level backup file, record all information about ownership, authorities, and privileges for the objects in the schema. (If necessary, contact IBM Support for assistance.) After restoring, use TRANSFER OWNERSHIP statements to manually reassign ownership, and GRANT statements to manually reassign missing authorities and privileges.
RTC 108049 When using the web console to load data from a local file, data transfer is extremely slow for files larger than 2 GB. All Versions Do not attempt to load large amounts of data directly from a local file. Instead, transfer the data file from the local system to the /mnt/clusterfs/scratch directory of a host server file system (this might require administrator intervention) and upload it from there. When using the web console to upload the data, click the Server button to indicate the new location of the data file.
RTC 108036 When using the web console to load data from an AWS S3 data source, the load operation sometimes fails with an "/mnt/blumeta0/home/dsadm/sqllib/db2profile: No such file or directory" error, even though the console indicates that the operation was successful. All Versions Do not use the web console to load data from an AWS S3 data source. Instead, use the LOAD CLPPlus command.
RTC 108099 The Db2 Warehouse client container currently uses Internet Protocol Version 4 (IPv4) catalogs that will not work properly with IPV6. All versions

If you plan to use IPV6, at the Db2 Warehouse client CLI, issue the following commands to re-catalog the client container as a TCPIP6 node:

db2 catalog tcpip6 node nodealias remote ipv6addr server port

db2 catalog database bludb as alias at node nodealias

For example:

db2 catalog tcpip6 node node0101 remote 2001:cdba:0001:0002:abcd:0001:0003:1234 server 50000

db2 catalog database bludb as blutests at node node0101
RTC 107662 The Db2 Warehouse Orchestrator cannot be used to update an MPP system to V2.12.0 or V3.0.0. All versions earlier than 2.12.0 Follow the procedure described in " Updating IBM Db2 Warehouse (Linux) ".
RTC 107166 Db2 Spatial Extender capability is not available in the client container. All versions Use Db2 Spatial Extender in the common container only.
RTC 107006 On the HOME dashboard, the status information displayed by the Database availability widget is refreshed every 5 to 10 minutes. Consequently, the displayed status and the actual current status can be out of sync for a period of up to 10 minutes. 2.9.0 and later Refer to the status message that is displayed under the top banner of the console. This message indicates whether the database is currently connected or disconnected.

Resolved Issues
RTC/GitHub number Resolved Issue Affected versions Workaround First version to contain fix
GH 594 Clicking the "About" link on the home page of the Db2 Warehouse console results in an error. 3.10.0 To display the version of the currently deployed Db2 Warehouse image, issue the following command:
    docker exec -it Db2wh version		 11.5.1.0-CN1
GH 37 When you use the Db2 Warehouse console to attempt to back up or restore a database, the console displays a "Check TSM status failed" error message and the attempt fails. Consequently, you cannot use the Db2 Warehouse console to back up or restore a database. 3.8.0 - 3.9.0 To backup or restore a database, do not use the console. Instead, use the db_backup and db_restore commands. 3.10.0
RTC 108923
An attempt to apply the license file sometimes results in the following error due to incorrect end-of-file (EOF) control characters:
LIC1407N  You are trying to register an invalid license certificate file.
For example, if you transfer a license file from a Windows system to a Linux system, some EOF control characters might retain the Windows format.
 3.7.0 - 3.8.0
To resolve this:  
  1. As a root user, issue the following command to open a bash shell to the head-node container:
    docker exec -it Db2wh bash
  2. Change to the directory where the license file is saved. For example, if, on the host server, the license file is saved in /mnt/clusterfs, on the head-node container, issue the following command
    cd /mnt/blumeta0
  3. Issue the following command to convert the license file to Unix format:
    dos2unix <filename>
  4. From inside the container namespace, issue the following command to apply the license:
    manage_license -a /mnt/blumeta0/<filename>
 3.9.0
(none)
 In the Db2 Warehouse Version 3.4.0 Enterprise Edition image that was originally made available in the Docker Store, the product menu, which is located on the left side of the web console, is empty. This problem has since been corrected; however, if you downloaded the product image for Version 3.4.0 from the Docker Store shortly after it was made available, you might still encounter this problem. 3.4.0 In the Db2 Warehouse web console, open the product menu. If the menu is not empty, there is no need for you to do anything. If it is empty, retrieve the latest Db2 Warehouse Version 3.4.0 Enterprise Edition image from Docker Store and update your Db2 Warehouse container with the newer image. 3.4.0
RTC 107250 On the Download Tools page, the link to download Aginity Workbench for Db2 ( http://www.aginity.com/workbench/dashdb/ ) is broken. All versions earlier than 2.11.0 Use the URL https://www.aginity.com/main/workbench-for-db2-dashdb/ instead. 2.11.0
RTC 106811 On a Power MPP system, an update attempt fails with the following error:
"Options file /mnt/bludata0/options.json not generated by head node0101-fab within the expected timeout."		 2.8.0 Retry the update. If the error persists, contact IBM Support. 2.9.0
RTC 105797 Although history mode is not supported on the Spark monitoring page in the web console, the page might not state that and might display incorrect information. 2.5.0 2.6.0
RTC 105767 The MONITOR > Systems > Connections and MONITOR > Systems > Table Performance web console options do not work for non-administrator users. 2.5.0 2.6.0
RTC 105718 In the web console, if you click SETTINGS > External User Management, switch between User management options (Internal, External LDAP, and External AD), and then try to open the console in a new window, a blank page is displayed. 2.5.0 When you try to open the console in a new window, append the word console to the URL. For example, if the URL is https://9.70.207.174:8443/ , use https://9.70.207.174:8443/console instead. 2.6.0
RTC 105533 You cannot use the dashDB_local_Swarm_install.sh script after using the docker_remote command. 2.4.0 2.7.0
RTC 104887 After an update, the value of the EXTBL_LOCATION database configuration parameter is reset to the default value of /mnt/blumeta0/home. All versions If you do not want to use the default value, set a different value. 2.6.0
RTC 104416 If you are deploying, updating, scaling in, or scaling out by using Docker Swarm, the dashDB_local_Swarm_install.sh script might show that the deployment, update, or scaling process is hanging, even though it is proceeding normally. 2.0.0 and later versions To monitor the the deployment, update, or scaling process, check the docker logs on the head node. The dashDB_local_Swarm_install.sh script does correctly indicate when the process is complete. 2.4.0
RTC 98691 In the web console, an error message is displayed when you try to run a query and export it as a .csv file by using the following steps:
  1. Click Administer > Tables.
  2. Select a table and then click Generate SQL.
  3. Click Run > Run selected and export > As csv.
The error message is as follows:

"Run service is currently unavailable. Please contact your administrator to restart the web console service and try again."		 1.7.0 Instead of performing step 3, click Run > Run selected and export > As xslx, and then save the .xlsx file as a .csv file.

If you already tried clicking Run > Run selected and export > As csv, wait approximately 1 minute before clicking Run > Run selected and export > As xslx and saving the .xlsx file as a .csv file.		 1.8.0
RTC 98617 The readme.txt file for the IBM dashDB Support Tools (dbtoolkit) does not list the specific Linux 32-bit runtime libraries that you must install. All versions Install the following three libraries:
  • zlib*
  • ncurses-libs*
  • libcom_err*
 1.7.0
RTC 98512 If the license for your MPP deployment expires and you try to apply a production license by using the web console or the command-line method, the license is applied to only the head node. If you then try to start dashDB Local, a failure occurs because a valid license does not exist on the data nodes. All versions earlier than 1.7.0 Update to dashDB Local v1.7.0, and then reapply the license by using the web console or command-line method. For information, see Updating IBM Db2 Warehouse and Converting from an IBM Db2 Warehouse trial license to a Production license . 1.7.0
RTC 97815 If you scale in or scale out a Swarm-deployed cluster by using the
dashDB_local_Swarm_install.sh script and specify the -p port_number parameter, you must specify this parameter before the -si or -so parameter. Otherwise, the following error is displayed:

Cannot connect to the Docker daemon. Is the docker daemon running on this host?		 All versions earlier than 1.8.0 If you specify the -p port_number parameter, specify it before the -si or -so parameter. 1.8.0
RTC 97045 If you use the Load Open Data option in the web console, there might be an excessive delay in returning results. 1.5.0 Log out of the console (do not simply close the browser), log back in, and use the Load Open Data option again. The data should be returned more quickly. If you continue to experience excessive delays, check your internet connection. 1.6.0
RTC 95397 Loading data by using the Load > Load from Cloud option in the web console fails with a "certificate not trusted" error if you specify Amazon S3 as the data source.

If you specify Swift as the data source, you must specify one of the following endpoints to be able to browse files:

https://dal05.objectstorage.softlayer.net/auth/v1.0
https://hkg02.objectstorage.softlayer.net/auth/v1.0
https://sng01.objectstorage.softlayer.net/auth/v1.0
https://lon02.objectstorage.softlayer.net/auth/v1.0
https://ams01.objectstorage.softlayer.net/auth/v1.0
https://tor01.objectstorage.softlayer.net/auth/v1.0		 1.3.0 - 1.4.1 1.5.0
RTC 94990 Loading data by using the Load > Load Twitter Data option in the web console fails with the following message when you try to get tweet counts:

There's a problem with submitting your search. Make sure you're using the correct syntax and try again. If this issue persists, try your search again later.		 1.2.0 - 1.4.1
  1. Click Load > Load Open Data.
  2. Specify any search value and click Search.
  3. Click Load > Load Twitter Data again.
  4. Reload your data.
 1.5.0

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCJDQ","label":"IBM Db2 Warehouse"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 February 2020

UID

swg27049193

Page Feedback