Table of contents

Creating a database deployment on the cluster (Db2)

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

Before you begin

Procedure

  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.
  6. On the Advanced configuration page:
    • Use the Oracle compatibility option to specify whether Db2 is deployed in Oracle compatibility mode (the DB2_COMPATIBILITY_VECTOR registry variable is set to ORA).
    • For Page size, specify 16K or 32K.
    • If you use Portworx storage, you must specify 4K block size.
  7. You can choose to keep your system data and user data together in a single storage location, or put them in separate locations. System data contains the information that is used by Db2 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.
  8. Specify the storage to use for the database.
    For the available options, see Configuring database storage for Db2.
  9. Click Next.
  10. Optional: Specify a new display name for the database.
  11. Ensure that the summary is correct and click Create.

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

  12. 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).
  13. Optional: After deploying, if you want to upgrade the Db2 license from Db2 Community Edition to Db2 Advanced Edition, follow the steps in Upgrading the license of a deployed Db2 service.

What to do next

Ensure that a user with Manage Catalog permissions approves the request. The request shows on the Publish to Catalog Requests tab on their home page.

After the request is approved, the database is available on the Data connections page. You can use the connection when you run automated discovery to import, analyze, and classify data from the database.

As the database administrator, you can: