In a PureScale environment, the sql is runs well manually on both partitions (members) 0,1 and from both members.
The DB2 agents fail to run the sql on member 1. This cause that if the table is locked from member 0 and tries to select to that table from members 0 and 1, the agent sees in the tree only the block and locked sessions from member 0.
In DB2, monitoring a PureScale environment does not display locks when they are performed between two members (for example, one member is locking another member). This is a known issue listed in the Foglight cartridge for DB2 product release notes.
© 2022 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz