Db2 Big SQL post-provisioning tasks

Important: IBM Cloud Pak® for Data Version 4.8 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.

Depending on your environment, you might have to do the following tasks after you provision a Db2® Big SQL instance.

Configure Db2 Big SQL to use datanode hostnames when connecting to the datanodes on the Hadoop cluster.
Configure Db2 Big SQL to connect to an IBM® Storage Scale object store.
Connect Db2 Big SQL to a Hadoop cluster with a manually managed Kerberos configuration.
If the cluster has more than one Db2 Big SQL worker, run the health check command after the provisioning is completed. For more information, see Running the Db2 Big SQL health check command.
If you configured Db2 Big SQL to connect to an on-premises object store, and the object store does not support Virtual Hosting of buckets, you might encounter some problems accessing the object store buckets. To resolve this problem, configure the alternative pathSyleAcess to the bucket. For more information, see Operations against an object store are hanging or timing out (Db2 Big SQL).