Troubleshooting problems in Db2 Big SQL

Use this information and these solutions to resolve problems that you might encounter with the Db2® Big SQL service.

Db2 Big SQL appears to be stuck at AutoConfigure step after installation (Db2 Big SQL)
After Db2 Big SQL is installed or after the head pod is restarted, Db2 Big SQL isn't ready and appears to be stuck on the AutoConfigure step.
Alter table operation returns DB21034E and SQLSTATE 5804 (Db2 Big SQL)
On HDP 2.6.5, an ALTER TABLE (HADOOP) statement might fail with DB21034E (SQLSTATE 5804).
Failing insert operations into a table that is partitioned by a column expression (Db2 Big SQL)
Insert operations into a table that is partitioned by a column expression might return an error (SQL5105N).
Operations against an object store are hanging or timing out (Db2 Big SQL)
Operations against an on-premises object store, such as CREATE TABLE, hang, or time out.
Investigating problems that are encountered during interactions with an object store (Db2 Big SQL)
You might encounter unexpected behavior when Db2 Big SQL is interacting with an object store.
Queries fail with SQL-5105 errors after you upgrade Db2 Big SQL (Db2 Big SQL)
After you upgrade from Db2 Big SQL 3.0.1, queries fail to run.
Queries are not using new worker pods (Db2 Big SQL)
After you scale up a Db2 Big SQL instance to add new worker pods, the new workers are not being used by queries.
Disk failures in local storage on workers (Db2 Big SQL)
When there is a disk drive failure on the local storage that a Db2 Big SQL worker pod is bound to, the pod terminates and goes into a CrashLoopBackOff state.
After upgrading Cloud Pak for Data, Db2 Data Management Console can't connect to Db2 Big SQL
After IBM® Cloud Pak for Data is upgraded, a connection no longer exists between IBM Db2 Data Management Console and Db2 Big SQL.