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 IC84461 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 / A10 - 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:                                              * 
* user using db2icrt                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Move to next fp.                                             * 
****************************************************************
Local Fix:
Ensure the /db2shareddisk/db2sdin1 is removed or is empty.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
V10 fp1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
03.01.2013
03.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList