Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC71623 Status: Closed

USING DB2CFEXP TO EXPORT CONNECTIVITY CONFIGURATION ON LINUX,
"SERVERTYPE" CAN DISPLAY INCORRECT OPERATING SYSTEM INFORMATION

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When using db2cfexp tool to export connectivity configuration on 
LINUX Operating System, 
its output can show incorrect "ServerType", which is not 
expected. The following example illustrates this: 
 
Installing a brand new server and DB2 installation with Linux 
x86_64 (installing the proper DB2 for Linux x86_64) and running 
db2cfexp as "db2cfexp /tmp/db2conf BACKUP" can generate the 
following incorrect output (error marked with'<<<<<'): 
 
[INST>db2inst1] 
instance_name=db2inst1 
NodeType=4 
ServerType=DB2OS390 <<<<< 
Authentication=SERVER 
DB2COMM=TCPIP 
 
The fix for this defect will correct this incorrect output.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* N/A                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When using db2cfexp tool to export connectivity              * 
* configuration on LINUX Operating System, its output can show * 
* incorrect "ServerType", which is not                         * 
* expected.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 8.                       * 
****************************************************************
Local Fix:
There is no workaround for this issue, but it can be ignored as 
it won't have impact on the DB2 environment.
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem fixed on DB2 Version 9.5 Fix Pack 8.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.09.2010
09.08.2011
09.08.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.