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 IC81219 Status: Closed

DB2ICRT DOES NOT RETURN AN ERROR WHEN THE .SSH DIRECTORY EXISTS AND
IT'S NOT EMPTY IN THE SHARED DISK

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
When creating an instance using a user managed GPFS cluster and 
the following directory exists, but it is not empty, there could 
be issues during ssh setup between the instance owner across the 
cluster. 
 
e.g. 
# ls /db2shareddisk/db2sdin1/.ssh/ 
authorized_keys 
 
This file may conflict with instance creation. 
 
After applying the fix, an error should be shown if the 
directory exists and it's not empty.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* purescale install                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* apply next fixpack                                           * 
****************************************************************
Local Fix:
Ensure the /db2shareddisk/db2sdin1 is removed or is empty.
Solution
V98
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84461 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.02.2012
03.01.2013
03.01.2013
Problem solved at the following versions (IBM BugInfos)
9.8.
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.5 FixList