|
Problem IC95450
|
Status: Geschlossen |
DB2GCF UTILITY UPDATES THE DB2NODES.CFG TO SHORT HOSTNAME INSTEAD OF FULLY QUALIFIED HOST NAME |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
During a TSA automated database partition failover, db2gcfg
updates the db2nodes.cfg file. In some cases this will be
updated
to the short name of the host instead of the fully qualified
hostname.
Example:
$ cat db2nodes.cfg
0 test04.torolab.ibm.com 0
1 test04.torolab.ibm.com 1
$ hostname (Run from test03)
test03.torolab.ibm.com
$ hostname (Run from test04)
test04.torolab.ibm.com
Online IBM.ResourceGroup:db2_db2inst1_0-rg Nominal=Online
'- Online IBM.Application:db2_db2inst1_0-rs
|- Offline
IBM.Application:db2_db2inst1_0-rs:test03
'- Online
IBM.Application:db2_db2inst1_0-rs:test04
Online IBM.ResourceGroup:db2_db2inst1_1-rg Nominal=Online
'- Online IBM.Application:db2_db2inst1_1-rs
|- Offline
IBM.Application:db2_db2inst1_1-rs:test03
'- Online
IBM.Application:db2_db2inst1_1-rs:test04
Online IBM.Equivalency:db2_db2inst1_0-rg_group-equ
|- Online IBM.PeerNode:test04:test04
'- Online IBM.PeerNode:test03:test03
Online IBM.Equivalency:db2_db2inst1_1-rg_group-equ
|- Online IBM.PeerNode:test04:test04
'- Online IBM.PeerNode:test03:test03
In the above setup, if I then run the "rgreq -o move
db2_db2inst1_1-rg" command as root, it will cause TSA to
failover database partition 1 from host test04 to ceha03. This
works, but the problem is that the db2nodes.cfg file is being
updated with the short hostname as seen below
:
$ cat db2nodes.cfg
0 test04.torolab.ibm.com 0
1 test03 0 ceha03
The correct behavior would be for the DBM to update the 2nd line
of the db2nodes.cfg as follows:
1 test03.torolab.ibm.com 0 ceha03.torolab.ibm.com
This is because the hosts OS hostname value is set to
'test03.torolab.ibm.com'. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 and Fix Pack 3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 Version 10.5 and Fix Pack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.08.2013
27.02.2014
27.02.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
