Release Notes
Abstract
The default DB2 OLTP pattern with HADR pattern in the DB2 pattern type V1.2.9.0 with DB2 10.5.0.10 on Linux platform fails to configure HADR properly.
Content
The following HADR pattern with DB2 pattern type V1.2.9.0 (as part of IBM PureApplication System V2.3.0.1 and IBM Cloud Pak System V2.3.0.1) when deployed on Linux platform, has cluster configuration errors:
• Default DB2 OLTP pattern with HADR and VIP for Linux
Problem
In PureApplication System V2.3.0.1 and IBM Cloud Pak System V2.3.0.1 that uses DB2 Pattern type V1.2.9.0, if you attempt to deploy Default DB2 OLTP pattern with HADR on Linux platform then HADR does not work correctly because of a known defect in DB2 V10.5.0.10.
In PureApplication System V2.3.0.1 and IBM Cloud Pak System V2.3.0.1 that uses DB2 Pattern type V1.2.9.0, if you attempt to deploy Default DB2 OLTP pattern with HADR on Linux platform then HADR does not work correctly because of a known defect in DB2 V10.5.0.10.
The pattern deployment is successful. However, HADR is not enabled on the database. This aspect is a known issue from DB2, and special builds are provided by the DB2 product development team to resolve the issue.
Resolution
This aspect is a known limitation. As a workaround, download the DB2 interim special fix from IBM Fix Central.
Refer to this direct link for downloading the fix:
3. Deploy the above-mentioned pattern along with the fix pack. See https://www.ibm.com/support/knowledgecenter/SSZQFR_2.3.0.1/doc/iwd/mpt_vsys_db2_fixpack_update.html.
DB2 10.5.0.10 Special Build 38328 for Linux
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Information%2BManagement&product=ibm/Information+Management/DB2&release=All&platform=All&function=fixId&fixids=special_38328_DB2-linuxx64-universal_fixpack-10.5.0.10-FP010%3A321876927197722112&includeSupersedes=0
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Information%2BManagement&product=ibm/Information+Management/DB2&release=All&platform=All&function=fixId&fixids=special_38328_DB2-linuxx64-universal_fixpack-10.5.0.10-FP010%3A321876927197722112&includeSupersedes=0
Complete these steps to apply the special fix pack when you deploy the pattern:
1. Log in to the IBM PureApplication System console or the IBM Cloud Pak System console.
2. Upload the DB2 fix pack to the IBM PureApplication System or IBM Cloud Pak System. See
https://www.ibm.com/support/knowledgecenter/SSZQFR_2.3.0.1/doc/iwd/mpt_vsys_db2_fixpack_upload.html.1. Log in to the IBM PureApplication System console or the IBM Cloud Pak System console.
2. Upload the DB2 fix pack to the IBM PureApplication System or IBM Cloud Pak System. See
3. Deploy the above-mentioned pattern along with the fix pack. See https://www.ibm.com/support/knowledgecenter/SSZQFR_2.3.0.1/doc/iwd/mpt_vsys_db2_fixpack_update.html.
4. Verify that the DB2 cluster after the pattern instance is in RUNNING state.
Verification steps
1. SSH to the primary DB2 Server virtual machine as a DB2 administrator.
2. Verify the DB2 cluster by issuing this DB2 command:
db2pd -ha
This solution is applicable when you plan to deploy the HADR pattern.
Note: If you deployed the HADR pattern instance, but the cluster is not configured correctly then follow these steps to recover from the error. The solution is to apply the DB2 interim fix.
3. Download the DB2 interim fix from IBM Fix Central as stated in the previous steps.
4. Upload the DB2 interim fix to IBM PureApplication System or IBM Cloud Pak System. See https://www.ibm.com/support/knowledgecenter/SSZQFR_2.3.0.1/doc/iwd/mpt_vsys_db2_fixpack_upload.html.
5. SSH to the primary DB2 Server virtual machine as a DB2 administrator.
6. Delete the cluster by using this command.
db2haicu -delete
7. SSH to the secondary DB2 Server virtual machine as a DB2 administrator and delete the cluster as done in the preceding step.
8. Apply the DB2 interim fix for an instance on both the virtual machines. See https://www.ibm.com/support/knowledgecenter/SSZQFR_2.3.0.1/doc/iwd/mpt_vsys_db2_fixpack_apply.html.
9. Verify the fix pack installation status by using this command on both the virtual machines.
db2level
10. Verify that the cluster is running by using this command.
db2pd -ha
11. If the cluster does not run after you apply the interim fix, then you must manually reconfigure the cluster. Complete these steps.
a. SSH to the DB2 primary virtual machine and run these commands.
- db2 start hadr on db hadrdb as primary
- db2haicu -f / tmp/primaryxmlfile
2 Default DB2 OLTP pattern with HADR pattern in DB2 pattern type V1.2.9.0 fails HADR configuration.
b. SSH to DB2 Secondary virtual machine and run these commands.
- db2 start hadr on db hadrdb as standby
- db2haicu -f /tmp/standbyxmlfile
12. Verify the DB2 cluster.
If the problem persists, contact IBM Support team for further assistance.
Verification steps
1. SSH to the primary DB2 Server virtual machine as a DB2 administrator.
2. Verify the DB2 cluster by issuing this DB2 command:
db2pd -ha
This solution is applicable when you plan to deploy the HADR pattern.
Note: If you deployed the HADR pattern instance, but the cluster is not configured correctly then follow these steps to recover from the error. The solution is to apply the DB2 interim fix.
3. Download the DB2 interim fix from IBM Fix Central as stated in the previous steps.
4. Upload the DB2 interim fix to IBM PureApplication System or IBM Cloud Pak System. See https://www.ibm.com/support/knowledgecenter/SSZQFR_2.3.0.1/doc/iwd/mpt_vsys_db2_fixpack_upload.html.
5. SSH to the primary DB2 Server virtual machine as a DB2 administrator.
6. Delete the cluster by using this command.
db2haicu -delete
7. SSH to the secondary DB2 Server virtual machine as a DB2 administrator and delete the cluster as done in the preceding step.
8. Apply the DB2 interim fix for an instance on both the virtual machines. See https://www.ibm.com/support/knowledgecenter/SSZQFR_2.3.0.1/doc/iwd/mpt_vsys_db2_fixpack_apply.html.
9. Verify the fix pack installation status by using this command on both the virtual machines.
db2level
10. Verify that the cluster is running by using this command.
db2pd -ha
11. If the cluster does not run after you apply the interim fix, then you must manually reconfigure the cluster. Complete these steps.
a. SSH to the DB2 primary virtual machine and run these commands.
- db2 start hadr on db hadrdb as primary
- db2haicu -f / tmp/primaryxmlfile
2 Default DB2 OLTP pattern with HADR pattern in DB2 pattern type V1.2.9.0 fails HADR configuration.
b. SSH to DB2 Secondary virtual machine and run these commands.
- db2 start hadr on db hadrdb as standby
- db2haicu -f /tmp/standbyxmlfile
12. Verify the DB2 cluster.
If the problem persists, contact IBM Support team for further assistance.
Original Publication Date
27 September 2019
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFQSV","label":"IBM Cloud Pak System Software"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"2.3.0.1","Edition":"All editions","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
06 May 2020
UID
ibm11073816