The libdb2tsa library which db2haicu depends on for interactions
with the cluster manager(TSA) has an explicit dependency on
libstdc++.so.5. RHEL 7.2 and SLES 12 both have libstdc++.so.6
installed by default. As a result the db2haicu utility fails as
follows on these platforms:
$ db2haicu
Welcome to the DB2 High Availability Instance Configuration
Utility (db2haicu).
You can find detailed diagnostic information in the DB2 server
diagnostic log file called db2diag.log. Also, you can use the
utility called db2pd to query the status of the cluster domains
you create.
For more information about configuring your clustered
environment using db2haicu, see the topic called 'DB2 High
Availability Instance Configuration Utility (db2haicu)' in the
DB2 Information Center.
db2haicu determined the current DB2 database manager instance is
'db2inst1'. The cluster configuration that follows will apply to
this instance.
db2haicu is collecting information on your current setup. This
step may take some time as db2haicu will need to activate all
databases for the instance to discover all paths ...
There was an error with one of the issued cluster manager
commands. The user can determine the cause of the error by
invoking 'db2instance -list' and 'db2cluster -list -alert'. The
db2diag.log for the current member and the DB2 Information
Center may provide additional details.
Furthermore, the following error message is logged to the
db2diag.log:
2016-04-13-16.30.50.313795-240 E2607E612 LEVEL:
Error
PID : 3174 TID : 46912497507328 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME: ip-10-0-0-12.us-west-2.compute.internal
FUNCTION: DB2 UDB, high avail services,
sqlhaInitVendorInfrastructure, probe:850
MESSAGE : ZRC=0x6964616F=1768186223
DATA #1 : String, 36 bytes
Error initializing HA Vendor Process
DATA #2 : unsigned integer, 4 bytes
1768186223
DATA #3 : String, 40 bytes
/home/db2inst1/sqllib/lib64/libdb2tsa.so
DATA #4 : String, 5 bytes
db2ha
DATA #5 : Pointer, 8 bytes
0x00002aaacc2170e0 |
