Deploying databases by using default patterns

You can deploy a DB2® database by using one of the default database patterns that are provided on the system, depending on the workload type and features that your environment requires.

Before you begin

You must accept licenses, and enable patterns before you can deploy a database.

Procedure

  1. In the console, click Patterns > Virtual Systems.
  2. Select one of the following options:
    Default DB2 BLU Datamart Pattern for Linux®
    Used for data warehousing. The data mart workload standard is optimized for analytics and reporting applications. This option also enables BLU Acceleration® for DB2 databases, and use in-memory caching and columnar storage.
    Default DB2 Datamart Pattern for Linux
    Used for data warehousing. The data mart workload standard is optimized for analytics and reporting applications. BLU Acceleration cannot be enabled with this option.
    Default DB2 OLTP Pattern for Linux
    Used for online transaction processing and provides a stand-alone database. The departmental transactional workload standard is optimized for transactional applications.
    Default DB2 OLTP Pattern with HADR for Linux
    Used for online transaction processing. The departmental transactional workload standard is optimized for transactional applications. With this option selected, the high availability and disaster recovery (HADR) feature creates a primary and standby database, and also provides support for database cloning.
  3. In the pane that displays the details for the database pattern that is selected, click Deploy.
  4. In the Deploy Pattern window, configure the settings for the default database pattern.
    1. Configure the details for the database pattern deployment on the virtual machine:
      Name
      The name that you want to assign the database pattern.
      Environment Profile
      The pre-created profile that contains information such as the virtual machine name, IP address, and the cloud group. When you select an environmental profile, the Cloud Group and IP Group fields automatically populate based on the settings of the profile that you select.
      Priority
      The priority that the pattern is deployed in comparison to other patterns that are deployed on the system, at the same time.
      SSH key
      You can add key pair or the system if you already have one, or you can generate a key pair for the virtual machine.
      Schedule Deployment
      Define when you want to begin the deployment, and the duration that the deployment runs.
  5. Configure the attributes for the database pattern. The options and settings that are displayed varies based on the type of default pattern you select.

    If you are using the Default DB2 OLTP Pattern with HADR for Linux pattern, you can use an iSCSC disk as the TSA's tiebreaker for the DB2 HA instance is supported. An iSCSI target disk must already be created to use this option. Specify the iSCSI target disk's IP address and the IQN ID for that iSCSI target disk in the iSCSI Target IP address and iSCSI Target Name attributes. These two attributes are optional. If you specify these two attributes, the DB2 HADR instance configures the TSA to use the iSCSI tiebreaker. Otherwise, the instance configures the TSA to use the network tiebreaker.

  6. Click Prepare to Deploy.
  7. Click Deploy to confirm the settings and deploy the database.

    While the database deploys, you can view the details such as the database deployment status, middleware configuration, virtual machines, and the database history on the Instance > Virtual Systems page.