|
Problem IC71548
|
Status: Closed |
USING DB2CFEXP TO EXPORT CONNECTIVITY CONFIGURATION ON LINUX, "SERVERTYPE" CAN DISPLAY INCORRECT OPERATING SYSTEM INFORMATION |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - 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. 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. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 Fix Pack 10. *
**************************************************************** |
| 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.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
First fixed in DB2 Version 9.1 Fix Pack 10. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71623 IC71624 IC71907
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.09.2010
30.11.2010
30.11.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
