The following db2diag.log errors are reported when the
'db2instance -instance db2inst2 -list' command is run as root:
2018-05-18-15.46.06.759068+480 I4098A339 LEVEL: Error
PID : 41615730 TID : 1 PROC :
db2instance
INSTANCE: db2inst2 NODE : 000
HOSTNAME: purehost1
EDUID : 1
FUNCTION: , , , probe:3258
DATA #1 :
libsqlha: sqlhaGetObjectAttribute() call error from wrapper lib
36
2018-05-18-15.46.06.762013+480 I4438A288 LEVEL: Error
PID : 41615730 TID : 1 PROC :
db2instance
INSTANCE: db2inst2 NODE : 000
HOSTNAME: purehost1
EDUID : 1
FUNCTION: , , , probe:3259
DATA #1 :
clus err msg :
The db2diag.log error messages are being generated because we
are querying for resource dependencies defined against the
following db2dump mount resource as shown in lssam, but none
exist:
Online IBM.ResourceGroup:db2mnt-db2dump-rg Nominal=Online
'- Online IBM.Application:db2mnt-db2dump-rs
|- Online IBM.Application:db2mnt-db2dump-rs:purehost3
|- Online IBM.Application:db2mnt-db2dump-rs:purehost4
|- Online IBM.Application:db2mnt-db2dump-rs:purehost1
'- Online IBM.Application:db2mnt-db2dump-rs:purehost2
It is normal that dependencies against the db2dump mount
resource are not defined because it is not a critical file
system essential for database functionality.
If these db2diag.log error messages are being observed, they can
be safely ignored. It is expected to see these db2diag.log error
messages if the DIAGPATH dbm cfg parameter is set to a
GPFS(Spectrum Scale) mount path. |
