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

SQL405N REPORTED BY DB_MEMBERS AND DB_PARTITIONS TABLE FUNCTIONSIF NETNAME
EXCEEDS 128 CHARACTERS IN DB2NODES.CFG

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The output column SWITCH_NAME of the DB_MEMBERS and
DB_PARTITIONS table functions is defined as VARCHAR(128), but
netname values up to 255 characters are supported in the
db2nodes.cfg file. If a netname with a length > 128 characters
is used, these interfaces will return SQL405N when queried.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fix pack.                              *
****************************************************************
Local Fix:
Use a netname in the db2nodes.cfg that is less than or equal to
128 characters.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fix pack.                              *
****************************************************************
Comment
Problem was first fixed in DB2 UDB Version 11.5 fix pack 6
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.04.2021
11.06.2021
11.06.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)