Known issues and limitations for Db2 Big SQL

The following known issues and limitations apply to Db2 Big SQL.

For information that apply to backup, restore, or other platform-related operations, see Known issues and limitations for IBM® Software Hub.

For additional solutions to problems that you might encounter with Db2 Big SQL, see Troubleshooting problems in Db2 Big SQL.

Known issues

Db2 Big SQL has the following known issue.

When HTTP proxy is enabled through IBM Software Hub, pod restarts might cause Db2 Big SQL statements and queries to subsequently fail

Applies to: 5.2.0 and later

To work around the problem, run the following command on the Db2 Big SQL head node:

rah sudo sv restart db2uapi

The network configuration refreshes after approximately 5 to 10 seconds, allowing communication between the pods in the Db2 Big SQL instance. Queries will now complete successfully.

Limitations

Db2 Big SQL has the following limitations:

  • HBase tables are not supported.
  • Transactional tables are not supported.
  • Tables that are created in Db2 Big SQL are not propagated to Apache Atlas if Atlas is installed on the remote Cloudera Data Platform (CDP) Private Cloud Base cluster.
  • The LOAD command is not supported.