Upgrading your Db2 Warehouse Developer Edition license certificate key

Db2 Warehouse for Red Hat OpenShift can be upgraded from the Developer Edition by applying a new license activation key.

1. Encode your Db2 Warehouse license to base64 by running the following command::

   LICENSE_KEY="./dashdb_c.lic"
   cat ${LICENSE_KEY} | base64 | tr -d '\n'

   Save the encoded output, as you will add it to your YAML file later in this procedure.
2. Log in to your OpenShift® cluster and use the command line interface (CLI) get the name of your Db2uCluster or Db2uInstance custom resource:

   For Db2uCluster deployments:

   oc get db2ucluster
   

   For Db2uInstance deployments:

   oc get db2uinstance

   The following is a sample output from a successful command to get the name of your custom resource:

   NAME     STATE   AGE
   db2u-sample        Ready   1d

   Set an environment variable with the name:

   INSTANCE_NAME="db2u-sample"

3. Edit the custom resource.

   For Db2uCluster deployments:

   oc edit db2ucluster ${INSTANCE_NAME}
   

   For Db2uInstance deployments:

   oc edit db2uinstance ${INSTANCE_NAME}

4. In edit mode, locate the license key under spec in the YAML file and add the encoded string from step 1 as a value key, as shown below:

   spec:
     license:
       value: <ENCODED STRING FROM STEP 1 GOES HERE>

5. Save and close the YAML file. The following sample output confirms that an edit has been made:

   # oc edit db2ucluster ${INSTANCE_NAME}
   db2ucluster.db2u.databases.ibm.com/db2ucluster-sample edited

6. For the new license to take effect, delete the Db2® engine pods for the Db2uCluster or Db2uInstance:

   oc delete $(oc get po -l type=engine,formation_id=${INSTANCE_NAME} -oname)
   

7. Once the new Db2 pod is ready, verify the updated Db2 Warehouse license:

   oc exec -it  c-${INSTANCE_NAME}-db2u-0 -- su - db2inst1 -c "db2licm -l"