Release notes

IBM® Db2® Big SQL v7.1.0.0 provides full-function SQL query capability with Cloudera Data Platform (CDP) support and security and performance benefits.

These release notes contain:

New features overview

  • The ANALYZE command has been enhanced. Synopsis data that is related to statistics collection is no longer stored in a table’s directory. When this enhanced version of the ANALYZE command runs against a table for the first time, any existing synopsis data for that table is deleted. You can update the configuration to revert to the previous behavior.
  • Row and column access control (RCAC) is available. Ranger security support for Db2 Big SQL now includes masking and row-level filter policies in the Hadoop SQL and Db2 Big SQL plugins.
  • Db2 Big SQL is integrated with Apache Atlas in this release.
  • Db2 Big SQL now has JSON web tokens (JWT) support.
  • New SYSHADOOP table functions are supported in this release.
  • Db2 Big SQL supports IBM Spectrum® Scale.

Summary of other new features and capabilities:

Installation and upgrade
  • Upgrade from Db2 Big SQL 5.0.4 and 6.0.0 on Hortonworks Data Platform (HDP) to version 7.1.0 is available.

For details of these features and capabilities, see the What's new topic.

Known issues

Known issues exist related to Db2 Big SQL.

Known issues in Db2 Big SQL 7.1.0

There are no known issues to report at this time.

Known issues in CDP 7.1.3

CREATE HADOOP TABLE succeeds, but subsequent statements fail with NoSuchObjectException error
In a cluster with Ranger installed but not enabled for Db2 Big SQL, the CREATE HADOOP TABLE statement succeeds in creating the table, but subsequent statements, such as INSERT and SELECT, fail with a NoSuchObjectException error.

To work around this problem, add the bigsql user to the Hadoop SQL policies, even when Ranger is not enabled for Db2 Big SQL.

Known issues in Db2 Big SQL 7.0.0

Load into transactional tables is not supported
Data load operations against transactional tables are not supported in this release. For more information, see Transactional tables in Db2 Big SQL and LOAD HADOOP statement.
Db2 Big SQL on CDP limitations
  • Db2 Big SQL is installed by command line and not through Cloudera Manager.
  • Db2 Big SQL management is provided at minimal levels through Cloudera Manager.
  • YARN integration is not supported.
  • Db2 Big SQL supports CDP 7.0.3.
  • Patch management is not supported.
  • Migration from previous versions of Db2 Big SQL to version 7.0.0.0 is not supported.
  • Importing Hive authorizations is not supported.
Db2 Big SQL head node is stopped when you remove a dead node
When you remove a dead node, the Db2 Big SQL head node is stopped, and you must manually restart the head node by running the Db2 Big SQL cluster administration utility with the -restart option: ./bigsql-admin -restart.
Tip: To verify that the head node is restarted, log on to the head node as the bigsql user, and run the command bigsql status.
If HA is enabled, bigsql-admin -restart triggers a failover
In this scenario, the primary head node shuts down before the standby head node shuts down, and a failover operation is initiated. The standby head node becomes the primary head node for a short period of time until it shuts down as well. When everything restarts, the old standby head node becomes the primary head node. If you want the original primary head node to be the primary head node again, run the following command: ./bigsql-admin -triggerFailover.

Some operations, such as the ./bigsql-admin -autoConfigure command, cause Db2 Big SQL to restart which, in turn, triggers a failover. It is recommended that failover be disabled (./bigsql-admin -failoverController Disable) before running this command.

Db2 Big SQL fails to start after client Kerberos authentication was enabled due to a change in the location of the bigsql keytabs
In this scenario, the bigsql start command fails with SQL1365N db2start or db2stop failed in processing the plugin "IBMkrb5". Reason code = "10". To avoid this issue, append the following line to /home/bigsql/.bashrc on all Db2 Big SQL nodes:
export KRB5_KTNAME=/home/bigsql/.keytabs/bigsql.service.keytab
Data read failure (SSLHandshakeException) when SSL is enabled for the Java™ KMS for HDFS encryption
This is a JVM security configuration issue with JVM Transport Layer Security (TLS) versions on CDH. In a typical scenario, the Java Key Management Server (KMS) requires the TLSv1.2 protocol, but the client declares that it can support a maximum level of TLSv1. The IBM JDK version that is bundled with Db2 Big SQL supports TLS v1.2, but the client does not set this level by default. To avoid this issue, override the default TLS version by setting the com.ibm.jsse2.overrideDefaultTLS property to true. Run the following commands on the Db2 Big SQL head node.
Note: Before running the following bigsql-config -set command, run bigsql-config -get scheduler.java.opts to retrieve the current values of the Java heap settings (-Xms and -Xmx). Adjust the following bigsql-config -set command to retain those current values of the Java heap settings.

db2set DB2_JVM_STARTARGS="-Xnocompressedrefs ${ODP_JVM_STARTARG} -Dlog4j.configuration=file://${BIGSQL_HOME}/conf/log4j.properties -Dbigsql.logid.prefix=BSL-\${DB2NODE} -Dcom.ibm.jsse2.overrideDefaultTLS=true"

bigsql-config -set "scheduler.java.opts=-Xms512M -Xmx2G -Dcom.ibm.jsse2.overrideDefaultTLS=true"
Now restart Db2 Big SQL, and it should be able to connect to the Java KMS. Load, insert, or select operations over the encryption zone should complete successfully.
Pre-installation check utility fails to run
The pre-installation check utility fails to run with the following error message in the log file:
[ERROR] - File /home/bigsql/.bash_logout is not owned by bigsql.

To resolve the problem, run the following command:

sudo chown -R bigsql:hadoop /<Big SQL user's home directory>

For example,

sudo chown -R bigsql:hadoop /home/bigsql