Enabling PureData® System for Operational Analytics workloads

Important: IBM Cloud Pak® for Data Version 4.6 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.6 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

When deploying Db2® Warehouse, you can specify to use IBM PureData® System for Operational Analytics (PDOA), but the capability is not automatically enabled and you must take manual steps to use it.

To use this capability, the Db2 registry variable DB2_WORKLOAD must be set to PUREDATA_OLAP. However, even when you specify to use PDOA during database deployment, the value for this variable stays at ANALYTICS.

To enable a PDOA workoad, follow these steps:

Get the name of the head Db2 Warehouse pod by running this command:

oc get po -l name=dashmpp-head-0

Here's an example return from the command:

NAME                              READY   STATUS    RESTARTS   AGE
c-db2wh-1604709629237569-db2u-1   1/1     Running   0          51m

Exec into the pod and run the following command to disable the Wolverine high availability monitoring process:
```
wvcli system disable -m "Stop HA"
```
Become the Db2 Warehouse instance owner and stop Db2 Warehouse.
```
su - db2inst1
db2stop force
rah 'ipclean -a'
```
Set the DB2_WORKLOAD registry variable to PUREDATA_OLAP:
```
db2set DB2_WORKLOAD=PUREDATA_OLAP
```
Start Db2 Warehouse:
```
db2start
```
Run the following CLP script as Db2 Warehouse instance owner to re-run Db2 autoconfigure so that the database tuning aligns with the changes in database memory allocation for the workload PUREDATA_OLAP:
```
db2 -tvf ${DB2CFG_PERSIST}/db2_autoconf.clp
```
Stop and start Db2 Warehouse so that the changes take effect:
```
db2stop force
rah 'ipclean -a'
db2start
```
Exit out of the Db2 Warehouse instance owner shell:
```
exit
```
Re-enable Wolverine and then check the high availability status:
```
wvcli system enable -m "Start HA"
wvcli system status
```