APAR status
Closed as fixed if next.
Error description
When enabling Big SQL HA in an environment where bigsql user is an LDAP user, typically /etc/passwd will not have an entry for the user as it is not a local user. During HA enablement, if an entry in /etc/passwd is not found, installation process adds an entry for bigsql user with the default home directory, /home/bigsql. Since the actual home directory of bigsql is not /home/bigsql, HA enablement will fail with the following symptom. bash: line 1: db2pd: command not found Failed to verfiy HA on primary, command output was: Last login: Wed Jun 13 14:59:26 UTC 2018
Local fix
If bigsql user is an LDAP user and the home directory is not /home/bigsql, then an entry can be added to /etc/passwd prior to adding second head node to the cluster. Note, this step needs to be performed on both head nodes. echo "bigsql:x:"´id -u bigsql´:´id -g bigsql´"::<home directory of bigsql user>:/bin/bash" >> /etc/passwd
Problem summary
See problem description
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
PI99773
Reported component name
IBM BIG SQL
Reported component ID
5737E7400
Reported release
502
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-06-29
Closed date
2020-08-17
Last modified date
2020-08-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"502","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
18 August 2020