Configure DB2 on SUSELinuxServer

Article Title: Configure DB2 on SUSELinuxServer. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

This article first examines DB2 UDB for Linux®, UNIX®And Windows®IBM DB2 in®Universal Database™The Data Partition Feature (DPF) has advantages in performance and scalability. Then, install and configure DB2 with DPF function on SUSE Linux Enterprise Server. You will also learn some important concepts and design considerations, which will help you quickly master the installation of DPF in SUSE Linux Enterprise environment.

Introduction

When a database is composed of two or more database partitions, and each database partition stores part of the table data in each of the tables, it is a database partition. Different partitions can be on different computers or on the same computer (logical partition ). In this type of database, data is hashed Based on the storage location to identify which database partition stores the data. A database partition consists of its own data, indexes, configuration files, and transaction logic. In earlier versions of DB2, database partitions are called nodes or database nodes. However, we use partition in this article ). Logical partitions share resources on the same computer where they are located.

In a partitioned database, a table can be distributed in one or more database partitions. The idea behind partitioning is to distribute the data of a table in multiple partitions, store some rows in the table in one partition, and store other rows in other partitions. Database Manager (DBM) Automatically splits SQL requests into sub-requests to process data retrieval and updates. Then, these sub-requests are executed in parallel in the corresponding database partition. Table partitioning into multiple partitions is transparent to users, which means that although data is physically stored in multiple database partitions, but access is like a place.

Figure 1 shows a single partition running on a machine, similar to the absence of DPF:

Figure 1. Single partition on a single machine

The following two figures show how DPF actually works. Figure 2 shows that DPF is used on three machines, with each machine having a partition.

Figure 2. use high-speed communication for a partition on each machine

Note that the high-speed communication is used here. This can be a TCPIP network used between machines. Figure 3 below shows the three partitions on the same machine. Here, interval-based communication is implemented in the memory, rather than through a network (DB2 _ FORCE_FCM_BP is enabled by default on all Linux platforms ).

Figure 3. Three partitions on the same machine communicate through memory

Note that in the previous figure, the symmetric multi-processor (SMP) can also be replaced with a single processor. However, SMP servers are more common in DPF environments.

The partition key is composed of one or more columns in the table, allowing you to select how to partition their data. You can use database partition groups and tablespaces to determine which database partitions the table data is distributed.

User interaction is performed through a database partition, that is, a coordinator partition for this user. The Coordination partition and the application program run on the same database partition, or for remote applications, the Coordination partition runs on the database partition connected to the application. Any database partition can be a coordinated partition.

 

[1] [2] [3] [4] [5] [6] [7] [8] [9] Next page