home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65895 Status: Geschlossen

DB2HAICU XML IMPORT ONLY SUPPORTS ONE VIRTUAL IP PER PARTITION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
db2haicu xml import only created one virtual IP per partition 
when 3 were defined: 
 
    <DB2Partition dbpartitionnum="0" instanceName="bcuaix"> 
      <VirtualIPAddress baseAddress="9.23.20.196" 
subnetMask="255.255.252.0" networkName="db2_public_network_0"/> 
      <VirtualIPAddress baseAddress="10.1.1.40" 
subnetMask="255.255.255.0" networkName="db2_FCM_network"/> 
      <VirtualIPAddress baseAddress="10.1.2.34" 
subnetMask="255.255.255.0" networkName="db2_MGMT_network"/> 
      <Mount filesystemPath="/db2path/bcuaix/NODE0000" /> 
      <Mount filesystemPath="/db2fs/bcuaix/NODE0000" /> 
      <NPlusMNode standbyNodeName="bluejay16" /> 
    </DB2Partition> 
 
The import completed without any error: 
 
Creating domain bcudomain in the cluster ... 
Creating domain bcudomain in the cluster was successful. 
Configuring quorum device for domain bcudomain ... 
Configuring quorum device for domain bcudomain was successful. 
Adding network interface card en12 on cluster node bluejay14 to 
the network db2_public_network_0 ... 
Adding network interface card en12 on cluster node bluejay14 to 
the network db2_public_network_0 was successful. 
Adding network interface card en12 on cluster node bluejay15 to 
the network db2_public_network_0 ... 
Adding network interface card en12 on cluster node bluejay15 to 
the network db2_public_network_0 was successful. 
Adding network interface card en12 on cluster node bluejay16 to 
the network db2_public_network_0 ... 
Adding network interface card en12 on cluster node bluejay16 to 
the network db2_public_network_0 was successful. 
Adding network interface card en11 on cluster node bluejay14 to 
the network db2_FCM_network ... 
Adding network interface card en11 on cluster node bluejay14 to 
the network db2_FCM_network was successful. 
Adding network interface card en11 on cluster node bluejay15 to 
the network db2_FCM_network ... 
Adding network interface card en11 on cluster node bluejay15 to 
the network db2_FCM_network was successful. 
Adding network interface card en11 on cluster node bluejay16 to 
the network db2_FCM_network ... 
Adding network interface card en11 on cluster node bluejay16 to 
the network db2_FCM_network was successful. 
Adding network interface card en0 on cluster node bluejay14 to 
the network db2_MGMT_network ... 
Adding network interface card en0 on cluster node bluejay14 to 
the network db2_MGMT_network was successful. 
Adding network interface card en0 on cluster node bluejay15 to 
the network db2_MGMT_network ... 
Adding network interface card en0 on cluster node bluejay15 to 
the network db2_MGMT_network was successful. 
Adding network interface card en0 on cluster node bluejay16 to 
the network db2_MGMT_network ... 
Adding network interface card en0 on cluster node bluejay16 to 
the network db2_MGMT_network was successful. 
Adding DB2 database partition 0 to the cluster ... 
Adding DB2 database partition 0 to the cluster was successful. 
Adding DB2 database partition 1 to the cluster ... 
Adding DB2 database partition 1 to the cluster was successful. 
Adding DB2 database partition 2 to the cluster ... 
Adding DB2 database partition 2 to the cluster was successful. 
Adding DB2 database partition 3 to the cluster ... 
Adding DB2 database partition 3 to the cluster was successful. 
Adding DB2 database partition 4 to the cluster ... 
Adding DB2 database partition 4 to the cluster was successful. 
All cluster configurations have been completed successfully. 
db2haicu exiting ... 
 
Only the last defined virtual IP was created: 
 
# lssam -g db2_bcuaix_0-rg 
Online IBM.ResourceGroup:db2_bcuaix_0-rg Nominal=Online 
        |- Online IBM.Application:db2_bcuaix_0-rs 
                |- Online 
IBM.Application:db2_bcuaix_0-rs:bluejay14 
                '- Offline 
IBM.Application:db2_bcuaix_0-rs:bluejay16 
        |- Online 
IBM.Application:db2mnt-db2fs_bcuaix_NODE0000-rs 
                |- Online 
IBM.Application:db2mnt-db2fs_bcuaix_NODE0000-rs:bluejay14 
                '- Offline 
IBM.Application:db2mnt-db2fs_bcuaix_NODE0000-rs:bluejay16 
        |- Online 
IBM.Application:db2mnt-db2path_bcuaix_NODE0000-rs 
                |- Online 
IBM.Application:db2mnt-db2path_bcuaix_NODE0000-rs:bluejay14 
                '- Offline 
IBM.Application:db2mnt-db2path_bcuaix_NODE0000-rs:bluejay16 
        '- Online IBM.ServiceIP:db2ip_10_1_2_34-rs 
                |- Online 
IBM.ServiceIP:db2ip_10_1_2_34-rs:bluejay14 
                '- Offline 
IBM.ServiceIP:db2ip_10_1_2_34-rs:bluejay16 
 
 
The balanced warehouse requires 3 virtual IPs on the coordinator 
partiiton
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* InfoSphere Balanced Warehouse                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Only one Virtual IP could be defined for a partition in      * 
* theXML imported by db2haicu. If more than one was defined,   * 
* onlythe last defined IP resource would be created.           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2V97 fix pack 2                                 * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem fixed in db2V97 fix pack 2
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66569 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.01.2010
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList