Adding mount points to enable replication on Db2 Warehouse

If you plan to use replication with Db2® Warehouse, you must specify two extra mount points that are used for the replication infrastructure when you deploy Db2 Warehouse.

About this task

You specify the mount points with the Docker run command when you initialize the Db2 Warehouse container.

Procedure

Issue the following docker run command concurrently on all node hosts. Do not attempt to wait until the command finishes running on one node host before issuing it on another. This command pulls, creates, and initializes the latest Db2 Warehouse container on each node host. 
docker run -d -it --privileged=true --net=host --name=Db2wh -v /mnt/clusterfs:/mnt/bludata0 -v /mnt/clusterfs:/mnt/blumeta0 -v /bludrmqdata:/mnt/bludrmqdata -v /bludrdb2data:/mnt/bludrdb2data store/ibmcorp/db2wh_ee:v3.4.0-db2wh-linux

Where:

  • /bludrmqdata is a clustered, POSIX-compliant file system to be used for IBM® MQ persistent queue data.
  • /bludrdb2data is a clustered POSIX-compliant file system to be used as the data-streaming path for Db2 column-organized tables.
Note: The nodes that you specify must be independent file systems and not directories in the same file system that is used for Db2 Warehouse. Otherwise you might create I/O bottlenecks on either the MQ persistent queue data or Db2 column-organized table data.

What to do next

See Deploying IBM Db2 Warehouse for more details on the deployment process.