IBM DB2

Public Check Items

Check the database environments of the production end where DB2 databases reside.

1. When a database environment is configured at the production end where hosts running Linux, AIX or HP-UX are deployed, the mount points of the file system used by the database cannot be nested. For example, mount points /testdb/ and /testdb/database1/ are nested.
2. Before configuring a DB2 database, obtain the instance name, user name, and password of the DB2 database. The instance name is the DB2 database instance name. The user name is that of the system user of the DB2 database instance. Usually, the user name is the same as the instance name. The password is that of the system user. The DB2 database password does not support special characters !;"'(),·=\', otherwise, database authentication will fail when creating a protected group.
3. For the DB2 PowerHA cluster, you need to ensure that the host names of the hosts where the production DB2 databases reside must be same as the specified node names in PowerHA cluster. Otherwise, protected groups will fail to be created.
4. In AIX, the logical volumes used by the file systems of DB2 databases and those used by raw devices of tablespace cannot belong to one volume group.
5. Check and configure environment variables.

   The eReplication Agent starts to protect data consistency between DB2 databases only after you have configured environment variables for DB2 databases at the production end respectively. You are advised to configure environment variables before installing the eReplication Agent. If you have installed the eReplication Agent, restart it after configuring environment variables. For detailed operations, see System Maintenance > System Maintenance Commands > Starting the eReplication Agent in the OceanStor BCManager 8.2.0 eReplication User Guide.

   

   Before configuring environment variables, check the default shell type of user rdadmin on the eReplication Agent.

   • In AIX, if the shell type is bash, modify the .profile file under the rdadmin home directory. If the shell type is csh, modify the .cshrc file under the rdadmin home directory.
   • In Linux, if the shell type is bash, modify the .bashrc file under the rdadmin home directory. If the shell type is csh, modify the .cshrc file under the rdadmin home directory.
   • In HP-UX, if the shell type is bash, modify the .profile file under the rdadmin home directory. If the shell type is csh, modify the .cshrc file under the rdadmin home directory.

   This document uses shell type bash in AIX to modify the .profile file as an example.

   1. Use PuTTY to log in as root to the application server where the eReplication Agent is installed.
   2. Run the TMOUT=0 command to prevent PuTTY from exiting due to session timeout.
      

      After you run this command, the system continues to run when no operation is performed, resulting in a risk. For security purposes, you are advised to run exit to exit the system after completing your operations.

   3. Run the su - rdadmin command to switch to user rdadmin.
   4. Run the vi ~/. xxx_profile command to open the .profile file in the home directory of user rdadmin.For example, run the vi ~/.bash_profile command in the Red Hat operating system.
      

      Set xxx based on the site requirements.

   5. Press i to go to the editing mode and edit the .profile file.
   6. Add the following variables to the .profile file. Table 1 describes related environment variables.

      DB2_HOME=/home/db2inst1/sqllib 
      PATH=$PATH:$DB2_HOME/bin:/usr/sbin:/sbin 
      DB2INSTANCE=db2inst1 
      INSTHOME=/home/db2inst1 
      export DB2_HOME PATH DB2INSTANCE INSTHOME     

      

      In Linux, you need to add the VCS script path in the PATH variable, for example, PATH=$PATH:$DB2_HOME/bin:/usr/sbin:/opt/VRTS/bin:/sbin.

      Table 1 System variables

      Variable	Value	Example
      DB2_HOME	Installation directory of a DB2 instance	DB2_HOME=/home/db2inst1/sqllib
      PATH	The bin folder under the home directory of a DB2 instance user	PATH=$PATH:$DB2_HOME/bin:/usr/sbin:/sbin
      DB2INSTANCE	Name of a DB2 instance	DB2INSTANCE= db2inst1
      INSTHOME	Home directory of a DB2 instance user	INSTHOME=/home/db2inst1

   7. After you have successfully modified the .profile file, press Esc and run :wq! to save the changes and close the file.

Check Items at the Production End

Check the database configuration at the production end.

eReplication of the current version supports DR for DB2 databases on AIX, Linux, and HP-UX. DB2 databases that can be protected by eReplication must meet the following requirements:

• Installation directories of DB2 instances must reside on local disks or independent storage devices and cannot reside on the same devices as databases for which DR is intended.
• Data and log files of the DB2 databases for which DR and protection are intended must be stored on LUNs provided by Huawei storage devices.
• If remote replication is performed on a DB2 database, LUNs used by the database must be in the same consistency group. If the database uses only one LUN, the LUN does not need to be added to a consistency group.

----End

Check Items at the Storage End

1. Ensure that LUNs used by production databases are paired in HyperMetro mode and the HyperMetro pairs are in normal status.
2. Check whether information about initiators of production hosts (cluster) and test hosts (cluster) is displayed on the array.
3. Check that the production LUN has been mapped to the production host (cluster). For a cluster consisting of hosts, ensure that the hosts included in the host group to which the primary and secondary LUNs are mapped are all the hosts only in the cluster.