|
Problem IT22113
|
Status: Closed |
"DB2INSTANCE -LIST" MAY NOT SHOW ALERTS WHEN "DB2CLUSTER -CFS -LIST -FILESYSTEM -DISK" IS ISSUED BY ROOT.
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Alerts may not be generated when "db2cluster -cfs -list
-filesystem -disk" command
is issued by root ID. Whereas if the "db2cluster -cfs -list
-filesystem -disk" command
is issued by instance user ID, alerts will be shown properly in
"db2instance -list".
Here is an example output:
$ db2cluster -cfs -list -filesystem fsname -disk (by instance
owner)
...
$ db2instance -list
ID TYPE STATE HOME_HOST CURRENT_HOST ALERT ...
-- ---- ----- --------- ------------ -----
0 MEMBER STARTED psm00 psm00 NO ...
1 MEMBER STARTED psm01 psm01 NO
128 CF PRIMARY pscf0 pscf0 NO
129 CF PEER pscf1 pscf1 NO ...
HOSTNAME STATE INSTANCE_STOPPED ALERT
-------- ----- ---------------- -----
pscf1 ACTIVE NO YES |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher *
**************************************************************** |
| Local Fix: |
- Set environment variable DB2INSTANCE= for the
root user using command "export DB2INSTANCE="
Or,
- Issue "db2cluster -cfs -list -filesystem fsname -disk" by the
instance user |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.08.2017
27.11.2018
27.11.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
