During db2haicu execution to add a VIP address. Db2haicu
incorrectly reads an ip address as being alive when it is not.
The return code is a non 0 so assumes it is alive.
Messages in the db2diag.log will look like this:
2013-06-07-18.54.22.370835+000 I421153A367 LEVEL: Info
PID : 13762668 TID : 1 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, high avail services, sqlhaIsHostAlive,
probe:100
MESSAGE : Pinging host to see if it is alive
DATA #1 : String, 14 bytes
192.180.79.180
2013-06-07-18.54.22.371201+000 I421521A424 LEVEL: Info
PID : 13762668 TID : 1 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, high avail services,
sqlhaInitVendorInfrastructure, probe:250
MESSAGE : Path to HA Vendor Wrapper Library resolved
successfully
DATA #1 : String, 37 bytes
/db2/lddd089/sqllib/lib64/libdb2tsa.a
2013-06-07-18.54.22.393739+000 I421946A361 LEVEL: Info
PID : 13762668 TID : 1 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, high avail services,
sqlhaInitVendorInfrastructure, probe:300
MESSAGE : Initalized the vendor process for
SQLOVEND_PIPE_COMM_MODE
2013-06-07-18.54.22.394214+000 I422308A293 LEVEL: Info
PID : 13762668 TID : 1 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, high avail services,
sqlhaInitVendorInfrastructure, probe:400
2013-06-07-18.54.22.394414+000 I422602A418 LEVEL: Info
PID : 13762668 TID : 1 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, high avail services, sqlhaIsClusterNodeAlive,
probe:200
MESSAGE : Arguments being written across the pipe
DATA #1 : unsigned integer, 4 bytes
15
DATA #2 : String, 14 bytes
192.180.79.180
2013-06-07-18.54.23.407134+000 I423021A603 LEVEL: Info
PID : 15532084 TID : 1 PROC :
db2havend
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop,
probe:7501
DATA #1 : String, 5 bytes
EINTR
DATA #2 : Hexdump, 4 bytes
0x09001000A0D4CB58 : 0000 0001
....
DATA #3 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE6B8 : 0000 0000
....
DATA #4 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE6BC : 0000 0001
....
2013-06-07-18.54.23.407687+000 I423625A1379 LEVEL: Info
PID : 15532084 TID : 1 PROC :
db2havend
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop,
probe:7502
DATA #1 : String, 11 bytes
isHostAlive
DATA #2 : Hexdump, 1 bytes
0x0000000110028451 : 02
.
DATA #3 : Hexdump, 4 bytes
0x09001000A0D86044 : 0000 0001
....
DATA #4 : Hexdump, 4 bytes
0x0FFFFFFFFFFFFFE0 : 0000 0009
....
DATA #5 : Hexdump, 8 bytes
0x0FFFFFFFFFFFE6D0 : FFFF FFFF FFFF FFFF
........
DATA #6 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE6C4 : 0000 2000
.. .
DATA #7 : Hexdump, 4 bytes
0x09001000A0CD0658 : 0000 0006
....
DATA #8 : Hexdump, 4 bytes
0x09001000A0D4CB58 : 0000 0001
....
DATA #9 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE6C8 : 0000 0000
....
DATA #10: Hexdump, 4 bytes
0x0FFFFFFFFFFFE6CC : 0000 0000
....
DATA #11: Hexdump, 4 bytes
0x0FFFFFFFFFFFE6BC : 0000 0001
....
DATA #12: Hexdump, 4 bytes
0x0FFFFFFFFFFFE6B8 : 0000 0001
....
2013-06-07-18.54.23.420626+000 E425005A279 LEVEL: Info
PID : 13762668 TID : 1 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME:
EDUID : 1
FUNCTION: DB2 UDB, high avail services, sqlhaIsHostAlive,
probe:80
******************************************
This results from a compiler issue. And to resolve this lowering
the optimization level.
No workaround available. |
