IBM Db2 Big SQL 7.1.0

Problems and workarounds: Security

Table Insert fails with "Illegal key size" error when HDFS transparent data encryption is enabled
See the workaround below to resolve a problem of failing INSERT.
If you have READ, WRITE, and EXECUTE permissions as Db2 Big SQL Ranger policies only on an external table's location and contents, and no DATAACESS privileges, you cannot create external tables
You cannot create an external table in Db2 Big SQL as a user with no DATAACCESS privilege, if you have READ, WRITE, and EXECUTE privileges on that location and its contents only in Ranger, and not in HDFS.
Error when querying a table in an encrypted zone on a cluster with Db2 Big SQL global impersonation enabled
You may encounter a SQL5105N error while querying a table which resides in an encrypted zone if you are using Db2 Big SQL global impersonation.
Kerberos error code 37 when connecting to Db2 Big SQL
Use these steps to resolve an Kerberos error code 37 returned on attempting to connect to Db2 Big SQL.
"Token expired" errors when running Db2 Big SQL statements on a Kerberized cluster
"KDC can't fulfill requested option while renewing credentials" errors when running Db2 Big SQL statements on a Kerberized cluster
When running Db2® Big SQL statements on a Kerberized cluster, you might encounter Kerberos key distribution center (KDC) errors about credentials renewal in the bigsql.log file.
db2audit fails when some nodes are down
The db2audit utility requires that all nodes in your cluster are running.

Parent topic: Problems and workarounds