IBM Support

IT19365: IN CASE OF SETTING UP DB2HAICU WITH MULTIPLE NIC CARDS, PROVIDE THE OPTION TO SKIP A CERTAIN NIC

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • In the case of multiple NIC cards, DB2 is smart to detect all
    the NIC cards, but if the customer does not want to use any
    NIC card, the process of skipping a NIC card is very
    unintuitive. The customer has to
    add the NIC to either a public or a private network and when
    db2haicu asks for a confirmation saying are you sure you want to
    add, that is when the customer can enter NO if they don't want
    to add that NIC.
    A better mechanism of bypassing NIC needs to be provided in
    db2haicu's interactive mode.
    

Local fix

  • There are two workarounds:
    1. Use the db2haicu's XML file option, or
    2. Use the workaround mentioned in the error description section
    using db2haicu's interactive mode
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Platforms                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 LUW v10.5 Fixpack 9 or Later.                 *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 LUW v10.5 Fixpack 9
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT19365

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-22

  • Closed date

    2018-03-15

  • Last modified date

    2018-03-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA50 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 March 2018