home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT04628 Status: Closed

DB2CLUSTER REPORTS DBI20027E ERRORS WHEN SETTING UP LOGIN BANNER VIA
/ETC/SSH/SSHD_CONFIG

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When setting up Banner via the /etc/ssh/sshd_config which 
contains the line: 
 
Banner /etc/issue 
 
And /etc/issue contains the banner content, 
 
 
db2cluster utility fails and reports the following errors : 
 
ERROR: DBI20027E  The GPFS cluster creation failed on host 
"db2host1". Failed 
command: "/opt/IBM/db2/V10.5/bin/db2cluster -create -cfs -host 
db2host1 -domain 
db2cluster_20140920143413 -disk /dev/hdisk4". 
 
The cluster log shows: 
 
 
2014-09-16-14.34.13.885713-240 E1945A1888           LEVEL: 
Warning 
PID     : 4456802              TID : 1              PROC : 
db2cluster 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: db2host1 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, 
sqlhaIsDB2RootlessSSHConfigured, probe:88 
DATA #1 : String, 8 bytes 
db2host1 
DATA #2 : String, 22 bytes 
root@db2host1 hostname 
DATA #3 : String, 1449 bytes 
db2host1 
DATA #4 : Boolean, 1 bytes 
false 
 
2014-09-16-14.34.13.886622-240 I3834A348            LEVEL: 
Warning 
PID     : 4456802              TID : 1              PROC : 
db2cluster 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: db2host1 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, 
sqlhaIsDB2RootlessSSHConfigured, probe:102 
MESSAGE : db2ssh is not available, falling back to ssh 
 
 
Syslogs will report the following errors: 
 
Sep 16 14:26:00 db2host1.ibm.com syslog:err|error Message 
forwarded from db2host1: haValidateDB2LOCSSH[4391028]: |586 
failed to execute dummy ssh| 
Sep 16 14:26:00 db2host1.ibm.com syslog:err|error Message 
forwarded from db2host1: haParseSSHOptions[4391028]: |951 
invalid arguments| 
Sep 16 14:26:00 db2host1.ibm.com syslog:err|error Message 
forwarded from db2host1: haParseSSHOptions[4391028]: |954 ssh 
usage failed| 
 
collecting a db2trace will show the contents of the banner: 
 
2194  data DB2 UDB high avail services 
sqlhaIsDB2RootlessSSHConfigured fnc (3.3.115.1369.0.88) 
   pid 3277456 tid 1 cpid -1 node 0 sec 21 nsec 625579882 probe 
88 
   bytes 1897 
 
   Data1    (PD_TYPE_DIAG_LOG_REC,1889) Diagnostic log record: 
 
   2014-09-22-08.50.45.390593-240 E1950A1888           LEVEL: 
Warning 
   PID     : 3277456              TID : 1              PROC : 
db2cluster 
   INSTANCE: db2inst1             NODE : 000 
   HOSTNAME: tyesqdb3 
   EDUID   : 1 
   FUNCTION: DB2 UDB, high avail services, 
sqlhaIsDB2RootlessSSHConfigured, probe:88 
   DATA #1 : String, 8 bytes 
   db2host1 
   DATA #2 : String, 22 bytes 
   root@db2host1 hostname 
   DATA #3 : String, 1449 bytes 
   ******************************************************* 
   * This system is for the use of authorized users only. 
* 
   * Use without authority or in excess of authority 
* 
   * constitutes a violation of company policy and may 
* 
   * constitute a crime.  All users are subject to having 
* 
   * all of their activities on this system monitored and 
* 
   * recorded.                              * 
   ********************************************************* 
   db2host1 
   DATA #4 : Boolean, 1 bytes 
   false
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 Fix Pack 5 or higher                    * 
****************************************************************
Local Fix:
Disable ssh messages (including banners) for an individual user 
is as follows: 
 
In the ~/.ssh directory for the user initiating the ssh, edit 
the 'config' file with the following line: 
LogLevel quiet
Solution
First Fixed in DB2 V10.5 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2014
19.03.2015
19.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList