Creating a database deployment on the cluster (Db2 Warehouse)

You create a database deployment on your cluster from the IBM® Cloud Pak for Data web client.

1. From the navigation, select Data > Databases.
2. Click Create a database.
3. Select the database type and version. Click Next.
4. In the Configure area, specify the number of nodes, memory per node, and CPU per node.

   The console checks your OpenShift® cluster for adequate memory and CPU resources to meet your specifications. An error message displays if inadequate resources are found. If this occurs, you must either reduce the amounts that you specified or add more resources to the cluster.

5. If you are using a dedicated node, click Deploy database on dedicated nodes and enter the node label in the Value for node label box.
   For more information, see Setting up dedicated nodes for your Db2 Warehouse deployment.
6. On the Advanced configuration page, specify the following options:
   • Whether Db2 Warehouse is deployed in Oracle compatibility mode (the DB2_COMPATIBILITY_VECTOR registry variable is set to ORA).
   • The number of Multiple logical nodes (MLN) to use for your deployment.
   • What type of workoad to use:
     • Operational Analytics: Sets the registry variable DB2_WORKLOAD to PUREDATA_OLAP to use IBM PureData® System for Operational Analytics.
     • Analytics: Sets the DB2_WORKLOAD value to ANALYTICS to set the default table organization to COLUMN for column-organized tables.
7. For database storage, you can choose to keep your system data and user data together in a single location, or put them in separate locations. System data contains the information that is used by Db2 Warehouse to manage and configure the database. User data is the main database data. If you choose Separate locations for all data, you must specify a storage volume type, a name, and a size for both storage locations. If you use Portworx storage, you must specify 4K block size.
8. Specify the storage to use for the database.
   For the available options, see Configuring database storage for Db2 Warehouse.
9. Optional: If you want Db2 Warehouse to be able to work with external tables from a cloud object storage provider, click Object Storage in the left pane. This option is available for MPP deployments (you must have specified at least two nodes in Step 5).

   Object storage enables Db2 Warehouse to read data from files and use the files as if they were regular database tables. You can specify either Amazon Simple Storage Service (S3) or Microsoft Azure Blob Storage (Azure).

   Enter your credentials for connecting to the selected storage provider. For S3, an SSL connection is the default but you can specify Disable SSL. With S3 you can also click Allow path-style access if you want to connect by using a path-style URL similar to https://s3.Region.amazonaws.com/bucket-name/key in the Object storage endpoint field.

10. Click Next.
11. Optional: Specify a new display name for the database.
12. Ensure that the summary is correct and click Create.
    You might have to wait 2 to 40 minutes, based on the number of worker nodes and amount of memory that were allocated to the deployment.

    The database is ready when it shows up as Available on the Databases tab.

13. When the database is ready, select Submit connection for approval from the action menu.
    Important: The connection to the database is not available in the catalog until the request is approved by a user with Manage Catalog permissions (for example, a Data Steward).