IBM Support

Network Time Protocol (NTP) configuration error during DB2 10.1 instance creation with pureScale feature on SLES11 SP2

Troubleshooting


Problem

During an instance creation on DB2 10.1 with pureScale feature on SLES11 SP2, db2isetup or db2icrt returns with a minor error. A detailed examination of the install log shows an error in the NTP configuration component during instance creation. The instance and other components however are created or configured successfully.

Symptom

During an instance creation on DB2 10.1 with pureScale feature on SLES11 SP2, db2isetup or db2icrt returns with a minor error. An examination of the install log reveals:

ERROR: The Network Time Protocol (NTP) daemon configuration failed on the following hosts: "pq103.torolab.ibm.com". NTP was not found, and, an error occurred during an attempt to configure and start the daemon. See the log file "/tmp/ntpcfg.log.000" on the affected hosts for more details. To ensure that clock-sensitive operations (such as, error-logging, monitoring and point-in-time recovery) run optimally across a distributed environment, the NTP service must be synchronized across all members. Ensure NTP is installed and configured correctly before using DB2 pureScale. For detail, please see Required steps in Post Install Recommendations.
Register NTP :.......Failure

All other components were installed and configured successfully.

Further analysis of the ntpcfg log file reveals:

:::: VALIDATING PLATFORM ::::
SuSE Linux detected.
:::: VALIDATING PORT ENTRY FOR NTP ::::
ERROR: Port reservation for NTP does not exist in /etc/services.

Cause

This is a program defect related to the ntpcfg script packaged with DB2 10.1.0.0 on SLES11 SP2.

Resolving The Problem

To prevent this NTP error from occurring, follow these steps:
1. Ensure that the DB2 program files are installed in each and every machine for the DB2 pureScale cluster. This can be accomplished via db2setup. Do not configure or create any instances at this time.

2. Go to the DB2 installation's instance subdirectory, where you will find the ntpcfg script file. Make a backup copy of this file using the following command (running as root):

    cp ntpcfg ntpcfg.bak

3. Run the following command to edit the ntpcfg script (assuming the default installation path for DB2 /opt/ibm/db2/V10.1 is used)
    sed -i 's/Protocol\$/Protocol/' /opt/ibm/db2/V10.1/instance/ntpcfg


4. Repeat steps 2 and 3 for all machines in the DB2 pureScale cluster.

5. Execute db2isetup (as found in the instance subdirectory of the DB2 installation path) to create and configure the DB2 pureScale instance.

If the instance has already been created, the user can either choose to drop the instance and use the work around as above, or can follow the manual steps to set up a NTP server and configure each machine in the DB2 pureScale cluster as NTP clients in the DB2 information center.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"High Availability - PureScale","Platform":[{"code":"PF016","label":"Linux"}],"Version":"10.1","Edition":"Advanced Enterprise Server;Enterprise Server;Express;Express-C;Personal;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21591243