From the db2diag.log we can notice this:
The error occurred because the db cfg parameter HADR_LOCAL_HOST
and the OS hostname value do not match.
```
7291682 2021-02-02-10.55.40.342821-300 E1094791721E658
LEVEL: Error
7291683 PID : XXXX TID : 139679589746496 PROC : db2haicu
7291684 INSTANCE: XXXXX NODE : 000
7291685 HOSTNAME: XXXXXX
7291686 FUNCTION: DB2 UDB, high avail services,
sqlhaUICreateHADR, probe:7924
7291687 MESSAGE :
ECF=0x90000531=-1879046863=ECF_SQLHA_INVALID_PARAM
7291688 Invalid parameter to SQLHA call
7291689 DATA #1 : String, 144 bytes
7291690 There is a mismatch between the local hostname value and
the HADR DB CFG value (HADR_LOCAL_HOST or localHost). Correct
this and re-run db2haicu.
7291691 DATA #2 : String, 10 bytes
7291692 xxxxxxx
7291693 DATA #3 : String, 10 bytes
7291694 XXXXXXX
7291695 DATA #4 : String, 10 bytes
7291696 XXXXXXXX
```
You can find their HADR_LOCAL_HOST and OS hostname values set as
follows:
```
HADR local host name (HADR_LOCAL_HOST) = XXXXXX
HADR local host name (HADR_REMOTE_HOST) = XXXXX
mismatch that the OS hostname value is lower-cased whereas the
HADR_LOCAL_HOST/HADR_REMOTE_HOST values are upper-cased. This
should be accepted as matching hostnames. |
